Documentation map

Find the canonical MARS document.

Public guides explain how to use MARS. Canonical harness docs define product promises, operating rules, feature completeness, delivery state, evidence, and decisions. Use this map when you need the owner of a rule, not just a helpful summary.

Start And Safe Trial

Use these when evaluating MARS for the first time or checking what can write files.

PathPurposeHeadlineUse whenDoc typeCanonical statusUsed by agents?
docs/index.htmlFront door and routing.Inspect, govern, and improve MARS.Getting the product shape and next evidence route.Public guideSummaryNo
docs/quickstart.htmlFirst successful run.Install MARS and run one target.Running the first safe local lifecycle.Public guideReferenceNo
docs/install-setup-reference.htmlInstall, setup, local inference, and recovery.Prepare the local runtime.Preparing or repairing local runtime setup.Public referenceReferenceNo
docs/shell-integration-reference.htmlPATH setup and shell repair.Make the command available.Fixing command lookup or shell integration.Public referenceReferenceNo
docs/auth-credentials-reference.htmlCredential boundaries and token indirection.Keep secrets out of repo docs.Checking secrets, tokens, and authentication boundaries.Public referenceReferenceNo
docs/adoption-guide.htmlEvidence-based evaluation guide.Adopt MARS without losing control.Trying safely, reviewing controls, piloting, and deciding rollout.Public guideSummaryNo

Daily Operation

Use these after MARS is installed and a target repo is ready.

PathPurposeHeadlineUse whenDoc typeCanonical statusUsed by agents?
docs/workflows.htmlTask-oriented flows.Run MARS from install to daily operations.Choosing the right command flow for a job.Public guideReferenceNo
docs/target-lifecycle-reference.htmlInit, upgrade, scan, start, serve, eject.Manage target harness lifecycle.Managing a target repo from init to removal.Public referenceReferenceNo
docs/operations-guide.htmlRun modes and controls.Operate the local MARS runtime.Starting, pausing, stopping, and recovering the runtime.Public guideReferenceNo
docs/dashboard-api-reference.htmlDashboard pages, controls, and APIs.Use local dashboard controls.Inspecting or integrating dashboard controls.Public referenceReferenceNo
docs/observability-guide.htmlLogs, traces, metrics, evidence, and recovery.Understand what happened.Reading logs, traces, metrics, and run evidence.Public guideReferenceNo
docs/troubleshooting-guide.htmlSymptom-driven recovery.Fix the common failure modes.Diagnosing and recovering from known problems.Public guideReferenceNo

Security, Governance, And Ownership

Use these when checking data boundaries, control, evidence, and recovery before increasing autonomy.

PathPurposeHeadlineUse whenDoc typeCanonical statusUsed by agents?
docs/security-governance-guide.htmlSecurity, ownership, guardrails, and evidence route.Govern MARS before trusting autonomy.Checking data, credentials, guardrails, trust, evidence, and recovery.Public guideSummaryNo
docs/safety-quality-guide.htmlTrust levels, guardrails, quality, and recovery.Bound autonomy and inspect quality.Checking trust, quality, telemetry, and recovery behavior.Public guideReferenceNo
docs/guardrails-reference.htmlGuardrail schema, severity, matching, hooks, recovery.Define repo-owned policy.Writing or reviewing repo-owned policy.Public referenceReferenceSometimes
docs/files-state-reference.htmlWhat files and local state MARS writes and removes.Know what MARS owns.Checking file ownership, local state, and eject cleanup.Public referenceReferenceNo
docs/configuration-reference.htmlLocal and target configuration.Configure without leaking secrets.Changing local or target configuration safely.Public referenceReferenceSometimes
docs/documentation-sync-guide.htmlNo-stale-docs workflow.Keep public and harness docs aligned.Keeping human docs and harness docs in sync.Public guideReferenceYes

Agent Team And Delivery Model

Use these to understand how ideas become governed work.

PathPurposeHeadlineUse whenDoc typeCanonical statusUsed by agents?
docs/planning-delivery-guide.htmlGoal, plan, BDD, ticket, evidence, release chain.From idea to shipped change.Understanding how intent becomes shipped work.Public guideReferenceYes
docs/roles-guide.htmlRoles, domains, modes, and handoffs.Understand the AI product team.Inspecting role responsibilities and handoffs.Public guideReferenceYes
docs/harness-guide.htmlTarget harness structure and customization.Work with the deployed harness.Reading or adapting a generated harness.Public guideReferenceYes
docs/checks-evidence-guide.htmlLocal check recording and evidence.Record proof, not vibes.Recording and reviewing local check evidence.Public guideReferenceSometimes
docs/release-update-guide.htmlSemantic release notes, assets, updates.Ship and update deliberately.Preparing release notes, assets, and updates.Public guideReferenceYes

Extension And Integration

Use these when connecting MARS to tools, models, code intelligence, and optional board flows.

PathPurposeHeadlineUse whenDoc typeCanonical statusUsed by agents?
docs/cli-reference.htmlFull command surface.Know the exact command.Looking up exact command syntax.Public referenceReferenceNo
docs/tools-mcp-guide.htmlUniversal tool surface and MCP bridge.Expose tools with trust levels.Exposing tools through trust-aware MCP flows.Public guideReferenceYes
docs/models-guide.htmlLocal inference, optional providers, evaluation, overrides.Choose models deliberately.Choosing local models or optional provider routes.Public guideReferenceSometimes
docs/code-intel-reference.htmlCode graph context, tools, metrics, validation boundaries.Use local code intelligence as evidence.Using code graph context and code-intel tools.Public referenceReferenceYes
docs/integrations-validation-guide.htmlOptional integrations and validation matrices.Validate the connected surfaces.Connecting optional tools, providers, and validation suites.Public guideReferenceSometimes
docs/harness-ecosystem/Interactive adoption explainer.Understand the ecosystem story.Explaining the system model and value case.Public guideSummaryNo

Canonical System Records

These documents are source-of-truth records for the foundation harness and generated target doctrine.

PathPurposeHeadlineUse whenDoc typeCanonical statusUsed by agents?
AGENTS.mdFirst-read agent guide and operating rules.How agents work in MARS.Inspecting the top-level operating rules.Canonical harness docSource of truthYes
README.mdRepository overview and user entry points.What MARS is.Starting from the repository overview.Repository guideReferenceSometimes
ARCHITECTURE.mdSystem architecture overview.How the runtime is shaped.Reviewing runtime architecture.Architecture referenceReferenceSometimes
docs/product-specs/Product promises and surfaces.What MARS promises.Checking product promises and surface area.Product specSource of truthYes
docs/goals/active.mdActive product and operating goals.What the system is trying to achieve.Checking the active goals.Canonical system recordSource of truthYes
docs/exec-plans/active/current-operating-plan.mdCurrent scheduled plan.What is being worked now.Checking the current scheduled plan.Canonical system recordSource of truthYes
docs/features/BDD feature contracts and business behavior.What done means.Checking feature completeness and business behavior.BDD contractSource of truthYes
docs/tickets/Ticket lifecycle and work state.What work exists and what evidence it needs.Checking ticket state and evidence needs.Canonical system recordSource of truthYes
docs/design-docs/Architecture and operating decisions.Why the system works this way.Reading architecture and operating decisions.Design decisionSource of truthYes
docs/roles/ROLES.mdRole registry.Who the agent team is.Checking the registered role model.Canonical harness docSource of truthYes

Validation And Evidence

Use these when proving a claim or replaying a validation path.

PathPurposeHeadlineUse whenDoc typeCanonical statusUsed by agents?
docs/validation/README.mdValidation matrix and report rules.How evidence is recorded.Recording or replaying validation evidence.Validation evidenceSource of truthYes
docs/validation/release-blockers.mdRelease blocker ledger.What blocks release confidence.Checking known release blockers.Validation evidenceSource of truthYes
docs/QUALITY_SCORE.mdRepo-visible quality and role-health score.How healthy the system looks.Inspecting visible quality and role-health signals.Quality evidenceSource of truthYes
CHANGELOG.mdVersioned user impact and release notes.What shipped and why.Checking shipped impact and version history.Release evidenceSource of truthYes
VERSIONCurrent semantic version.What version this checkout is.Checking the current semantic version.Release evidenceSource of truthSometimes

Generated And Reference Material

Use these for generated maps, runbooks, research, bundle contracts, and lower-level references.

PathPurposeHeadlineUse whenDoc typeCanonical statusUsed by agents?
docs/generated/README.mdGenerated reference catalog.What generated docs exist.Finding generated reference material.Generated referenceReferenceSometimes
docs/runbooks/README.mdOperational procedures.How to run repeatable operations.Following repeatable operational procedures.RunbookSource of truthYes when routed
docs/references/README.mdResearch and external references.What informed decisions.Checking research and external inputs.ReferenceReferenceSometimes
docs/references/mdn-technical-writing.mdTechnical writing principles.Write public docs people can use.Reviewing public documentation writing standards.ReferenceReferenceSometimes
docs/bundle-reference.htmlBundle and manifest contract.Know the harness bundle shape.Checking the generated harness bundle contract.Public referenceReferenceSometimes
docs/bundle-reference.mdMarkdown companion for bundle contract.Manifest detail for maintainers.Reading manifest detail in Markdown form.ReferenceReferenceSometimes
docs/guardrails-guide.mdMarkdown companion for guardrails.Guardrail usage context.Reading guardrail usage context in Markdown form.ReferenceReferenceSometimes