= ANCHOR.scm Specification

1. Overview

ANCHOR.scm is the intervention layer for the SCM Format Family. It’s a "drop document" that helps projects survive scope storms and get back on track.

When AI agents or projects drift from their intended path, an ANCHOR file provides:

• Authority Declaration - Who is issuing the intervention

• Purpose Statement - Why realignment is needed

• Directives - Specific actions to take

• SCM Review - Which SCM files need attention

• Verification - How to confirm success

2. SCM Format Family

This specification is part of the SCM Format Family:

Format	Repository	Purpose
META.scm	meta-scm	Constitutional authority, architecture decisions
STATE.scm	Companion to META	Project state tracking
ECOSYSTEM.scm	Companion to META	Ecosystem positioning
PLAYBOOK.scm	playbook-scm	Executable plans derived from META
AGENTIC.scm	agentic-scm	Operational gating for AI agents
NEUROSYM.scm	neurosym-scm	Symbolic semantics, proof obligations
ANCHOR.scm	anchor.scm (this repo)	Project recalibration/realignment

All formats are satellites of hyperpolymath/standards.

3. When to Use ANCHOR

Use ANCHOR.scm when:

• Scope Drift - Project has expanded beyond intended boundaries

• Direction Change - Strategic pivot requires explicit realignment

• Stock-Taking - Periodic review and verification of alignment

• Course Correction - AI agent has accumulated incorrect assumptions

4. Quick Start

4.1. 1. Create the ANCHOR file

Name it ANCHOR.scm or ANCHOR-[purpose]-[date].scm.

4.2. 2. Define Authority

(define authority
  '((superintendent
     (name . "Project Owner")
     (role . "owner"))
    (issued
     (date . "2026-01-03"))))

4.3. 3. State Purpose

(define purpose
  '((type . "scope-arrest")
    (summary . "Halt scope expansion and stabilize")))

4.4. 4. Add Directives

(define directives
  '((immediate
     ((action . "halt-new-features")
      (priority . "critical")))))

4.5. 5. Drop into Repository

Place in root or .machine_readable/ directory.

4.6. 6. Instruct AI

Tell the AI: "Go to the ANCHOR.scm file first."

See examples/ for complete examples.

5. Execution Pipeline Position

ANCHOR operates at the intervention tier - above normal execution:

INTERVENTION LAYER:
  ANCHOR.scm     ← Recalibration directives

EXECUTION PIPELINE:
  1. META validation
  2. AGENTIC gating
  3. NEUROSYM semantics
  4. PLAYBOOK derivation
  5. Execution
  6. ECOSYSTEM check
  7. STATE update

ANCHOR can override or reset any level of the execution pipeline.

6. Specification

The complete normative specification is in spec/ANCHOR-FORMAT-SPEC.adoc.

7. Repository Structure

anchor.scm/
├── spec/
│   └── ANCHOR-FORMAT-SPEC.adoc    # Normative specification
├── examples/
│   ├── minimal.scm                 # Minimal valid ANCHOR file
│   └── comprehensive.scm           # Full-featured example
├── .machine_readable/
│   ├── STATE.scm                   # Project state
│   ├── META.scm                    # Architecture decisions
│   └── ECOSYSTEM.scm               # Ecosystem position
└── README.adoc                     # This file

8. Contributing

Contributions are welcome. Please ensure:

• All changes follow the normative specification

• Examples validate against the spec

• SPDX license headers on all files

9. License

PMPL-1.0-or-later with Palimpsest philosophical overlay. See LICENSE.