Biography

Early technical work

Proctor's earliest sustained professional software work was in Java game development and online community operations. She began work associated with Hypixel in January 2021, where her public professional chronology describes responsibilities around Java server systems, game mechanics, and community management. 14 That combination placed code and its users in the same operating environment: server behavior affected moment-to-moment play, while community feedback exposed product and reliability problems quickly.

From April 2023 to April 2024, she worked with Sandbattle Studios as a Java game developer and project manager. The role joined feature development, interface work, and delivery coordination rather than separating engineering from project ownership. 14 Between June 2023 and September 2024, she also held a game development and project management internship associated with Riot Games, supporting cross-functional development and product-management work. 14

These overlapping roles established several themes that remained visible in her later systems work: online software has to be understandable under live use; engineering decisions become product behavior; and coordination costs can be as consequential as local code quality. The chronology is primarily documented through self-maintained professional profiles and is labeled accordingly in the bibliography. 14

Cross-disciplinary systems work

Proctor's route into systems engineering also included work outside software. During the summer of 2023 she worked at Luminous Gardens as an apprentice electrician and apprentice case manager. The maintained record describes field experience in electrical systems, troubleshooting, planning, and customer work. 14 In her own account, that period reinforced an interest in systems whose constraints are physical, observable, and consequential.

The combination of software, project coordination, community operations, electrical fieldwork, and business study produced a practice centered on whole systems rather than isolated implementation layers. Her later work on Gray follows the same pattern: language syntax, memory ownership, networking, database progress, cancellation, packaging, deployment, and evidence are treated as one connected operating contract.

Infrastructure consulting

From January to June 2025, Proctor worked at DOT GROUP as a systems infrastructure account manager and consultant. The role covered infrastructure delivery, workflow automation, project coordination, and account operations. 14 It expanded her work from a single application or game environment into the organizational path by which technical systems are selected, delivered, and maintained.

This period is presented in the public record as a bridge between product work and later platform engineering. It exposed the cost of fragmented tools and handoffs: a technically capable system can remain difficult to operate when configuration, ownership, failure reporting, and deployment are split across unrelated products.

Grayworth and the creation of Gray

Proctor co-founded Grayworth in March 2026 and became its Chief Technology Officer. 1 Grayworth is a software corporation developing products, platforms, and infrastructure; Gray is its flagship server platform rather than the full scope of the corporation. Proctor leads the language and the technical systems behind Grayworth's commercial software work.

Gray was developed around the proposition that more of the server-development experience should belong to the language itself. Instead of treating HTTP, database access, structured work, session behavior, deployment policy, and release evidence as an assembly of unrelated frameworks, Gray places them in a shared compiler/runtime contract. 24

In its RC9 milestone, the runtime expanded to production-capable native value handling across x86-64 and Apple Silicon, including ownership-safe byte operations, native dynamic JSON, collection reads and construction, dynamic call edges, request and response handling, explicit fallback, and cancellation behavior. The same release introduced structured task groups, bounded typed channels, cancellation-aware selection, cryptographic primitives, and expanded TLS lifecycle support. 24

RC10 was narrower. It corrected the HTTP fast path and the release-evidence chain: response framing was coalesced, response bodies could be borrowed for transmission, the comparison image became reproducible, Static-runtime execution received an explicit proof, and the registered PostgreSQL continuation route replaced an obsolete manual-poll fixture. Exact measurements and their limitations are kept in Grayworth's research and evidence records rather than converted into a universal language ranking. 23

Technical practice

Compiler and runtime

Proctor's Gray work crosses language syntax, typed lowering, NativeIR, JIT and Static AOT execution, runtime ABI design, ownership, native value representation, and fail-closed fallback. The project keeps Live and Static policies attached to the same source-level semantics while allowing qualified regions to execute natively. 24

Server I/O and data

The server work includes HTTP, TLS, JSON, PostgreSQL continuations, readiness-driven progress, checked cancellation, and request ownership. A central design goal is that a handler can remain direct in source while the compiler and runtime preserve its frame across socket and database readiness. 23

Release evidence

Gray's public engineering record emphasizes corrected-latency load testing, same-host controls, long-duration resource sampling, source and artifact identity, and explicit non-claims. The retained publications distinguish an observed value from an architectural interpretation and from a projection. 23 Proctor's ORCID and ISNI identifiers connect this technical authorship to a persistent public identity. 11 12

Education

Proctor completed dual-enrollment study in business administration and management at Saddleback College from 2025 to 2026, alongside secondary education at San Juan Hills High School. Her maintained educational record lists both as completed in 2026. 14

In 2026 she began studies in business administration and management through Rutgers Business School and in computer science and engineering through Rutgers University–New Brunswick. The Rutgers institutional directory provides a public affiliation record. 2

Selected works

Gray

Lead developer and language designerA commercial server language and runtime integrating application code, native networking, PostgreSQL continuations, adaptive deployment, developer tooling, and native execution.

Gray benchmark methodology

Technical leadA reproducible performance program covering corrected latency, saturation, long-duration stability, resource growth, database execution, and native backend behavior.

Grayworth

Co-Founder and Chief Technology OfficerA founder-led software company building commercial products and the high-performance systems behind them.

The technical works and datasets are first-party records. They are useful for identifying design, implementation, and stated methodology, but they are not presented as independent evaluation. 24 23

Identity and names

The preferred professional and citation name is Annabella Proctor. Annabella Adair-Proctor is retained as an alternate name for identity matching rather than a separate person. The canonical person record is https://annabellaproctor.com/#person.

Her researcher identifier is ORCID 0009-0000-0799-1757, and her International Standard Name Identifier is 0000 0005 3067 1646. 11 12 Grayworth has a distinct organizational ISNI, preserving the boundary between creator identity and corporate publisher identity. 13

From games to programming languages

The chronology of my work begins with software people were already using: Java game servers, game mechanics, interfaces, and online communities. Those responsibilities included both implementation and the coordination around it. My later infrastructure work extended that experience into delivery, automation, and the operation of larger technical systems.

Gray brings those areas together in a different form. The work includes the programming language itself, but also the runtime that executes a program and the server facilities that allow it to answer requests and work with databases. The project crosses boundaries that would otherwise sit in separate libraries, tools, and deployment systems.

The employment dates and role descriptions on this site come from my maintained professional record. The timeline retains the overlapping dates rather than presenting these roles as a sequence of non-overlapping jobs.

Gray in use

Gray is used by the production sites for Grayworth, GrayLanguage, Preflight, and AnnabellaProctor.com. The language and its applications are developed alongside one another: the websites are working uses of the runtime, while the documentation and evidence site make parts of that work available to readers.

GrayLanguage is the home of the language reference and tutorials. Grayworth presents the company and its engineering work. Preflight collects measurements and release evidence, with the conditions of a comparison kept alongside the results. These sites have different roles, even though they share a runtime.

A website running successfully is evidence of that application working in its environment. Benchmark results answer narrower questions about a particular fixture, implementation, and host. This biography keeps those two kinds of evidence separate; the current measurements belong in Preflight.

Research and technical authorship

My published technical work examines several parts of Gray’s design and operation. Sustained Corrected-Latency Qualification of an Integrated Server Language Runtime concerns performance qualification over time. Compiler-Hidden PostgreSQL Continuations for Direct-Style Server Programs addresses database execution and direct-style server code.

Cancellation-Safe Native Loop Lowering in the Gray Runtime focuses on the relationship between native execution and cancellation behavior. Typed SSA NativeIR for Semantics-Preserving JIT and Static AOT in Gray concerns a typed intermediate representation shared by just-in-time and ahead-of-time compilation.

The research folder links to the publication records for these four works. The source register also includes author profiles, identifiers, institutional records, and first-party documentation. Catalog inclusion, identity records, and technical measurements serve different purposes and are labeled accordingly.

Education alongside the work

My maintained educational history includes completed secondary education at San Juan Hills High School and dual-enrollment study in business administration and management at Saddleback College. It also lists business administration and management at Rutgers Business School and computer science and engineering at Rutgers University–New Brunswick as in progress.

The 2026–2030 ranges in the education record describe the listed periods of study. They are not claims of completed Rutgers degrees. The original institutional and professional-profile links remain available in the source register.

A personal place for the full record

This website is both a personal homepage and a place to keep the longer record of my work together. The desktop, glitter, and little game are the playful part. The biography, timeline, research, source register, press kit, and machine-readable identity files provide the detail behind it.

For a short introduction, use the press and biography kit. For employment and education dates, use the timeline. For name matching and persistent identifiers, use the identity record. For a specific technical claim, follow the source associated with that claim rather than treating this personal biography as independent verification.

Electronics and other tools

Beyond Gray, Annabella’s public GitHub includes projects for electronics and domain management. Wiretracks provides a browser workspace for schematic capture and PCB routing. PartCount focuses on component inventory for electronics labs and hardware teams. Domain Scout covers domain discovery, evaluation, and portfolio workflows.

These descriptions follow the public repository records, checked September 8, 2026.