ArcaneArcane
GitHubGet started

Docs

Arcane methodology references, lifecycle artifacts, and filesystem structure.

The Spell Loop

Arcane ships through one repeatable lifecycle: plan, scope, architect, implement, review, ship, loop.

The Spell Loop reference

spell plan → spell architect → [ spell implement → spell test → spell review ]* → spell ship

Lifecycle sequence

  1. Plan

    Capture intent and acceptance criteria before code moves.

  2. Architect

    Choose contracts, data flow, and risk posture before coding.

  3. Implement

    Ship the smallest coherent slice that meets acceptance criteria.

  4. Test

    Validate behavior with automated checks and coverage thresholds.

  5. Review

    Run adversarial QA and security review before merge.

  6. Ship

    Merge, release, observe, and feed learnings into the next plan.

Phases and artifacts

Each phase produces a concrete artifact so teams can audit intent, execution, and release quality.

Phase grid

Plan

Define reviewable intent

PRD

Architect

Resolve contracts and risk

stories.json + acceptance criteria

Implement

Deliver scoped code changes

feature branch updates

Test

Prove behavior and quality

passing suite at thresholds

Review

Apply adversarial scrutiny

review sign-off

Ship

Release and observe

merged, versioned release

Artifact matrix

ArtifactOwnerLocationPurpose
PRDProduct + Eng.arcane/templates/Defines problem, user value, and success metrics.
ADRArchitectureDECISIONS.mdCaptures irreversible design decisions and tradeoffs.
Story checklistDelivery leadTODO.mdTracks the scoped work and acceptance completion.
Review evidenceQA + Securityjournal/Records lint, test, and review outcomes per session.

Where it lives

Arcane writes governance, templates, and run history into a predictable `.arcane/` footprint.

Where it lives

  • .arcane/

    Root workspace for Arcane governance, templates, and generated context.

  • .arcane/governance/

    Standards, guardrails, and policy docs used by agents.

  • .arcane/templates/

    Reusable PRD, ADR, and execution templates.

  • .arcane/journal/

    Session logs and evidence trail for shipped changes.

Launch readiness

Launch prep tracks the final SEO, deployment, analytics, and DNS handoff checks before go-live.

Phase grid

Preflight

Confirm metadata, robots, sitemap, and static artifact validation are green.

Launch verification report

Cutover

Apply DNS records with planned TTL values and monitor propagation.

DNS change ticket with timestamps

Post-launch

Validate analytics ingestion and production route integrity after go-live.

Launch acceptance sign-off

Artifact matrix

ArtifactOwnerLocationPurpose
Production launch checklistRelease ownerspec/launch-handoff.mdTracks release readiness, launch window sequencing, and sign-off accountability.
DNS handoff notesOps + Platformspec/launch-handoff.mdDocuments required DNS records, TTL plan, and rollback path.
Analytics readinessEngineeringcomponents/analytics-bootstrap.tsxEnsures telemetry only initializes when explicit production flags are set.