Specification
Authoritative design documents for trevor. Spec-first rule: each iteration requires writing specs before implementation.
Documents
| Document |
Contents |
| Constraints |
Non-negotiable architectural constraints (C-01 – C-13) |
| Domain Model |
Entity definitions, state machines, field-level detail |
| Glossary |
Canonical domain terminology |
| Iteration Plan |
Ordered delivery plan |
Architecture Decision Records
| ADR |
Title |
Status |
| 0001 |
Frontend Framework: Datastar |
Accepted |
| 0002 |
Storage Architecture: Two-Bucket S3 |
Accepted |
| 0003 |
Database Strategy: SQLite → PostgreSQL |
Accepted |
| 0004 |
RO-Crate: Default Profile, Release-Only |
Accepted |
| 0005 |
Agentic Checking: Pydantic-AI + Statbarn |
Accepted |
| 0006 |
Metadata Lineage: Linear Versioning |
Accepted |
| 0007 |
Authentication: Keycloak OIDC + Local RBAC |
Accepted |
| 0008 |
Kubernetes Deployment Architecture |
Accepted |
| 0009 |
Notification Abstraction Layer |
Accepted |
| 0010 |
Two-Person Review Rule |
Accepted |
| 0011 |
Object Immutability + Checksum Verification |
Accepted |
| 0012 |
CR8TOR CRD Sync: Project + User Mapping |
Accepted |
ADR status legend
| Status |
Meaning |
Proposed |
Under discussion, not yet binding |
Accepted |
Binding — implementation must follow |
Superseded |
Replaced by a later ADR |
Deprecated |
No longer applicable |
Iteration specs