AlterMundi/daimon-matrix

daimon-matrix implements persistent beings that may have zero, one or many
simultaneously active embodiments.
The situated scopes are:
- /me: this embodiment, here and now;
- /we: embodiments of the same being;
- /tribe: beings joined by signed membership in one group; resource grants
and deliberately directed relationships remain separate;
- /species and /source: capability lineage and attributed ancestry.
Plurality is normal. A global admission mechanism prevents reuse of one
embodiment credential in two bodies; it must not collapse every embodiment of
the being into a singleton.
Current architecture and deployment
Start with current architecture and profiles and
CURRENT-STATE.md. CompAII, Eko and Oliva share one deployed
membership group; I/O recovery and future automatic group admission remain
separate unfinished increments. A delivery receipt is not model attention.
Current runtime CI selects affected contracts on Python 3.13.5. Metadata support
for Python 3.11+ is not a current multi-version qualification claim.
Historical release-candidate status
The integrated V0 Matrix baseline is merged at commit
75b34804f8d013d348129946c0cd541a4448e71d, tree
38f3edb002ac52aac2d51fbf533cb58c38b813c5. The historical package qualification was
0.1.0rc1, with 102 closed scenarios and Python 3.11 through 3.14. Those figures
record that RC checkpoint, not current CI or deployment.
Historical qualification is retained in RESUME.md. Current receiving
and service evidence belong in CURRENT-STATE.md.
Component boundary
daimon-matrix owns being-root continuity, canonical signed state, scopes,
relationships and grants, memory policy, synchronization, and communication
semantics. daimon-cluster owns body/incarnation lifecycle, storage and
resource-scoped admission/fencing. Neither side may infer the other's
authority.
Tribe Bridge is a superseded experimental transport. The stable successor is
Matrix plus Cluster, with no Bridge operational-state migration, compatibility,
fallback or dual-run requirement. Native Matrix /tribe and relationship
governance remain. Live removal, publication and archive still require their
separate human authorizations. The historical RC checkpoint above is not
evidence of stable qualification or current deployment. See the current
retirement policy.
This project is unrelated to the external Matrix.org protocol.
Runtime and evidence
The typed Python package includes threshold-separated identity/recovery
ceremonies, plural embodiment and incarnation authorization, encrypted
custody, append-only ledgers, replay-safe sync, deterministic projections, an
authenticated owner-local daemon, CLI/MCP clients, relationships and grants,
recipient-encrypted communication, source/publication contracts, and isolated