Chatto Architecture Inventory
Read the inventory index. It defines
the categories and documentation boundaries. Read only the categories relevant
to the task. Run a complete audit only when requested.
Update affected inventory files by default. For a review, audit, or request
for proposals, report findings without edits unless the user also requests
fixes. Report code defects separately; inventory work does not authorize
implementation changes.
Source Checks
Paths below are relative to the repository root.
| Category |
Check against |
| Runtime components |
Core construction, runtime units, service and worker constructors; record ownership and lifecycle. |
| Projections |
Projector registration, Subjects(), projection_subjects_test.go, and snapshot code; distinguish registered projectors from nested read models. |
| NATS resources |
Stream, KV, and Object Store creation calls; record retention, storage, backup status, and owner. |
| Subjects and events |
Subject helpers, persisted protobuf variants, and live publishers; check event tokens and aggregate subjects. |
| Runtime state |
KV operations and object-key construction; record encoding, TTL, backup status, and security properties. |
| Durable effects |
Workers and recovery tests; check durable triggers, retries, restart recovery, duplicate delivery, and multiple replicas. |
| Interfaces |
Declared protobuf services, API.Handlers(), API.OperatorHandlers(), and HTTP mounts; check authentication and listener boundaries. |
| Realtime delivery |
Protocol, handler, event models, and client event bus; check projection waits, authorization, queues, and failure behavior. |
Editing And Verification
- Link to source code and relevant decisions. Do not copy tables from other
categories or reproduce the generated per-RPC reference.
- Replace stale facts in place. Keep compatibility details only while they
affect current behavior or stored data.
- Distinguish unavailable operational data from a healthy zero value.
- Keep retired resources out of the current resource inventory.
- Update the index when categories change. Keep
docs/ARCHITECTURE.md as a
short link to the inventory.
- Verify changed claims against code and check source and document links.
- Report the categories checked and any unresolved findings. Do not describe
a partial check as a complete audit.
1---2name: chatto-architecture-inventory3description: Maintain Chatto runtime documentation in docs/architecture/ when runtime structures change, or audit it when requested.4---56# Chatto Architecture Inventory78Read [the inventory index](../../../../docs/architecture/INDEX.md). It defines9the categories and documentation boundaries. Read only the categories relevant10to the task. Run a complete audit only when requested.1112Update affected inventory files by default. For a review, audit, or request13for proposals, report findings without edits unless the user also requests14fixes. Report code defects separately; inventory work does not authorize15implementation changes.1617## Source Checks1819Paths below are relative to the repository root.2021| Category | Check against |22| --- | --- |23| Runtime components | Core construction, runtime units, service and worker constructors; record ownership and lifecycle. |24| Projections | Projector registration, `Subjects()`, `projection_subjects_test.go`, and snapshot code; distinguish registered projectors from nested read models. |25| NATS resources | Stream, KV, and Object Store creation calls; record retention, storage, backup status, and owner. |26| Subjects and events | Subject helpers, persisted protobuf variants, and live publishers; check event tokens and aggregate subjects. |27| Runtime state | KV operations and object-key construction; record encoding, TTL, backup status, and security properties. |28| Durable effects | Workers and recovery tests; check durable triggers, retries, restart recovery, duplicate delivery, and multiple replicas. |29| Interfaces | Declared protobuf services, `API.Handlers()`, `API.OperatorHandlers()`, and HTTP mounts; check authentication and listener boundaries. |30| Realtime delivery | Protocol, handler, event models, and client event bus; check projection waits, authorization, queues, and failure behavior. |3132## Editing And Verification3334- Link to source code and relevant decisions. Do not copy tables from other35 categories or reproduce the generated per-RPC reference.36- Replace stale facts in place. Keep compatibility details only while they37 affect current behavior or stored data.38- Distinguish unavailable operational data from a healthy zero value.39- Keep retired resources out of the current resource inventory.40- Update the index when categories change. Keep `docs/ARCHITECTURE.md` as a41 short link to the inventory.42- Verify changed claims against code and check source and document links.43- Report the categories checked and any unresolved findings. Do not describe44 a partial check as a complete audit.
chattocorp