The docs site was never published: GitHub Pages is not configured for this repository, so the workflow built and uploaded a site nobody served. docs/ is repository documentation — Markdown read in the repository, an editor, or the forge's file view — and does not need a renderer. Removed: - docs/.vitepress/config.mts, docs/package.json, docs/pnpm-lock.yaml (1620 lines), docs/pnpm-workspace.yaml - docs/index.md (the site's landing page) - .github/workflows/docs.yml (pnpm install, VitePress build, Pages deploy) - the docs build-artefact ignores from .gitignore Kept and corrected: - docs/prds/01-project-management.md linked its decision documents with VitePress root-absolute paths (/architecture/...), which only resolve under a site build. Repointed to repository-relative paths. - docs/architecture/generated-documentation.md named VitePress as the renderer throughout. Now records the renderer and publishing surface as an open decision, with the consequences stated: reference pages unrendered, no link checker, no authoring server. Also corrected three claims that were never true — the docsgen all/check subcommands and the docs:* tasks do not exist, and no pre-commit hook is installed. - .agents skills: build-and-env and docs-and-writing no longer describe a docs site to build; the diagnostics scripts drop .vitepress skip rules and the dead github_docs_build scan. Generated output is unchanged: docs/data/generated/contracts.json and the docsgen toolchain are untouched, and tools/ remains its own module.
4.2 KiB
Architecture Decision Index
Status: Approved foundation; domain and package reviews are ongoing
Date: 2026-07-28
Beads issue: archie-core-5d7
Purpose
This file is the navigation point for Archie's target architecture. It is deliberately short. Architectural decisions are separated by domain or requirement so an implementation task can load only the rules governing its scope.
Implementers MUST read the decision document for the domain or requirement they are changing. They MUST NOT infer permission to change neighbouring domains from a broader restructuring objective.
Global invariants
- Organise code around cohesive application responsibilities, not generic technical mechanisms.
- Domains own their behaviour, vocabulary, state, commands, events, policy implementations, runtime settings, and required service contracts.
- Domains do not depend on infrastructure or manipulate another domain.
internal/appowns composition;cmd/*remains thin.- Cross-domain work uses an explicitly owned command, event, or approved shared contract.
- Process boundaries are deployment choices and do not determine source-code ownership.
- Existing package names and boundaries have no presumption of survival.
The words MUST, MUST NOT, SHOULD, and MAY are normative.
Decision documents
| Scope | Authoritative document |
|---|---|
| Repository layout, domains, composition, deployments, and optional material | architecture/organisation.md |
| Dependency direction, domain contracts, infrastructure, commands, events, and wire contracts | architecture/dependencies-and-contracts.md |
External configuration, runtime settings, and dissolution of internal/config |
architecture/configuration.md |
| Persistent actor identity, ownership, lifecycle, and attribution | architecture/identity.md |
| Agent definitions, workflows, workflow executions, tools, and worker boundaries | architecture/agent-system.md |
| Personal-assistant interactions, messaging channels, and optional promotion into durable work | architecture/messaging-and-work-intake.md |
| Shared policy evaluation and domain-owned policy semantics | architecture/policy.md |
| Safe source/configuration changes, health supervision, and recovery | architecture/safe-change-and-recovery.md |
| Plugin framework, plugin implementations, and extension isolation | architecture/plugins-and-extensions.md |
| Generated references, deprecations, and changelog generation | architecture/generated-documentation.md |
| Remaining package destinations, data migrations, runtime cutover, and completion criteria | architecture/migration-decisions.md |
| Domain/feature research, design interview, and required handoff | architecture/package-review.md |
Deferred decisions
The remaining package-placement, data-migration, shared-mechanics, process- boundary, and cutover decisions are maintained in architecture/migration-decisions.md.
Each decision is made in its focused document after code-grounded review.