Documentation

flowchart LR
  arch[Architecture] --> agents[Agent team] --> flows[Business flows]
  arch --> data[Data model]
  arch --> api[Integration API]
  arch --> blocks[Building blocks]
  flows & data & api --> testing[How it is tested]
  testing --> coverage[Coverage]

The system

• The agent team
• Integration API
• Architecture
• Data model
• Data sources
• Features
• Glossary

Business flows

• Any college
• Campus life, the bus, jobs and mentors
• Jobs and careers
• Class-site sync
• Community
• When something goes wrong
• Drafts and approval
• Explaining a letter
• Meals for the week
• Money found and short months
• The operator
• Outcome measures
• Deadlines, plans and held time
• Playbooks
• Sensitive data
• Signing in
• Starting by text
• Weather and roads

How it is tested

• Running the factory on Google Cloud Build
• Coverage
• Exhaustive walks
• Gates
• Intent journeys
• Mutation testing and ratchets
• The 33 patterns, in operation
• The red team
• Walking in a real browser

Building blocks

• Campus services
• @zthr/egress
• @zthr/evidence
• @zthr/explore
• @zthr/gates
• @zthr/intent
• @zthr/models
• @zthr/operator
• @zthr/plain-language
• @zthr/privacy
• @zthr/review
• @zthr/runtime
• @zthr/store
• @zthr/twin-service
• @zthr/twins
• @zthr/ui

Decisions

• ADR 0001: Storage behind an interface, SQLite first
• ADR 0002: Hono server and a framework-free progressive web app
• ADR 0003: Deterministic first, models optional
• ADR 0004: The factory admits; people sign only what destroys

Every test file names the document it verifies, and every document lists its tests. The docs-linked gate fails the build when either side is missing.

Not affiliated with any educational institution. All data from public sources.