The methodology  /  v0.1

Ten artifacts. Each one stops a specific failure.

An artifact is a document you write once, keep current, and can point to when you or the AI need to know what the rules are. Documents beat intentions because a document can be reviewed, cited, and checked. Read the two load-bearing ones first: the technical plan and the hard rules. Everything else hangs off those.

Core plan
technical-plan.mdSettle architecture once, separately from execution.
build-guide.mdDecompose the plan into PR-sized, reviewable blocks.
testing-and-definition-of-done.mdReplace “it works” with a checkable “it is done.”
ci-spec.mdGuardrails as fail-closed CI checks.
Living logs
CLAUDE.mdWorkspace-level orientation for the AI collaborator.
BUILD-LOG.mdDone / Deviations / Next session, kept current.
DECISION-LOG.mdDecisions, made durable and reversible on purpose.
Review
PULL_REQUEST_TEMPLATE.mdMake review more than a rubber stamp.
ISSUE_TEMPLATE/Decision-needed, bug, and task templates.
Knowledge
knowledge-map/Structuring a proprietary knowledge base.
source-profiles.mdDecide how to handle each source type before ingesting any.
Design
design-system/One system, one rule that overrides convenience.