Shared principles and standards for the Tesserine ecosystem.
This repo holds the bedrock principles, design principles, and architectural decision records (ADRs) that define standards across all Tesserine components. Every repo — whether it builds infrastructure, runtime, or methodology — derives its standards from what lives here.
- agentd — container lifecycle daemon for autonomous agent sessions
- runa — cognitive runtime enforcing methodology topologies
- groundwork — contributor methodology plugin (first methodology)
- base — reference container image for agent sessions
Future repos inherit these principles by default.
- PRINCIPLES.md — seven bedrock principles organized as a topology (sovereignty, sequence, grounding, obligation to dissent, recursive improvement, transmission, verifiable completion)
- DESIGN-PRINCIPLES.md — sixteen engineering judgment principles governing how we think about code (elimination over accommodation, fix at the source, honest naming, correctness over optimization, architecture as communication, review discipline)
- EXIT-CODES.md — shared session-outcome exit code contract for runners and callers across the ecosystem
- REQUEST.md — canonical contract for the request artifact, the entry point that triggers a session
- RELEASE.md — release process for Tesserine cargo-workspace repos, formalized by ADR-0006
- RELEASING.md — commons-specific release ceremony for this docs and schemas repository
- ECOSYSTEM-RELEASE.md — ecosystem release manifest format and cross-repo verification contract
- schemas/ — versioned JSON Schemas that are the machine-checkable realizations of canonical artifact specs
- adr/ — architectural decision records that operationalize the principles
Each repo may have its own repo-specific ADRs that trace back to the shared principles defined here. This repo holds what is universal across the ecosystem; individual repos hold what is specific to their domain.
Open an issue or pull request on this repo. Changes to shared principles affect the entire ecosystem, so proposals should demonstrate that the change serves the ecosystem's trajectory, not just one repo's convenience.