Chapter 19: AegisGenera / Reference-Monitor Gateway

CH. 19 OF 19 NOT YET DRAFTED
Listen to this chapter
Can't play? Download the MP3 directly.

AegisGenera / Reference-Monitor Gateway

Confirmed unbuilt as of this manual's drafting — per James, directly, and consistent with a direct search of the full source zip, which contains no AegisGenera source anywhere. aegisgenera.com is referenced in CRC's own site navigation (Chapter 5) but has not itself been fetched or reviewed.

AegisGenera is referenced elsewhere as a "hardened reference monitor gateway" and vendor-agnostic compliance middleware. Two things in this manual's already-verified source material point at what its eventual role is likely to be, though neither is a confirmation:

  1. CRC's own Pillar 04 (Boundary) description (Chapter 5) names exactly the capabilities a reference-monitor gateway would need to implement: certificate-pinned endpoints, request signing, anomaly detection, circuit breakers, a governed endpoint registry, and GABA attestation (Chapter 11) for computer-use agents specifically. This is a strong structural fit for what AegisGenera is described elsewhere as being — but CRC's homepage doesn't actually name AegisGenera as the Pillar 04 implementation the way it explicitly names DXMachine for Consolidate and "Chandra Protocol + DXMachine" for Reduce/Close. That specific attribution is inferred, not stated.

  2. Chapter 10's positioning of AegisGenera as the actual end-state client offer — per James directly, the real answer to "how does a client get control and security" is a sovereign, self-hosted deployment running their own AegisGenera boundary, not a seat on shared chandrahub infrastructure. This tells us AegisGenera's commercial role (the thing a client ultimately runs to be sovereign) even though it doesn't yet tell us its technical one in detail.

Nothing in this manual's reviewed source describes AegisGenera's actual architecture, request flow, or how it would integrate with a worker instance's own network boundary (Chapter 8) or the auth gap flagged in Chapter 15. This chapter should be drafted once real AegisGenera source or documentation exists, using the same verify-before-writing discipline as every other chapter in this manual — not extrapolated further from the two adjacent-but-indirect references above.

← All chapters  ·  General Reasoning, Inc. · Birmingham, Alabama · Manual v1.0
Join the beta. Two ways in: we can help you set up a closed beta -- use the Industry Configurator to generate a custom personality for your organization, then email the resulting JSON to inquiries@genreason.com along with the subdomain you'd like for an unpublished test site (integration assistance available). Or explore the public-facing Chandra Marshaller directly -- a number of companies are already populated there, no setup required. See current beta deployments.