Notes and working language

This page is a place for architecture notes, naming experiments, internal framing, and draft summaries. It should be read as a notebook, not as proof that a system is deployed, validated, conscious, or complete.

How to read this page

• Some terms here are conceptual or organizational rather than externally verified product facts.
• Repository structure can support a description of intended architecture, but not every described feature should be assumed live.
• Public-facing claims should stay anchored to visible repositories, running surfaces, and confirmed deployments.

Current bounded summary

Across the public repos, there is evidence of ongoing work on agent-oriented software, orchestration patterns, UI structure, deployment materials, and documentation. There is also a layer of internal naming and canon language that benefits from being clearly separated from product status claims.

Useful themes preserved here

• Architecture: rings, layers, routing, memory, and coordination can be discussed as design language.
• Governance: approval gates, auditability, and bounded action are useful operational ideas.
• Consolidation: the website, a0, and aimmh overlap enough that terminology should be normalized.

What was removed

• Claims that a page itself demonstrated consciousness or settled capability.
• Statements implying deployment, validation, or runtime status without direct confirmation.
• Language treating internal labels as externally established fact.

Next consolidation steps

1. Keep this page explicitly framed as notes.
2. Move repo-specific summaries to Projects and a0.
3. Create one glossary page later if recurring terms still need a stable public reference.

hmmm: the language is cleaner now, but a final public glossary and long-term naming hierarchy still need Erin’s preference.