Purpose

The ACP Production Charter governs how artifacts are interpreted, transformed, published, and archived within ACP without inflating authority, laundering legitimacy, or collapsing diagnostics into governance.

It exists to prevent a recurrent institutional failure mode:

Interpretation becomes persuasive before it becomes constrained.

ACP treats interpretation as an institutional act, not a rhetorical one.

Scope

This Charter applies to all ACP-related work, including but not limited to:

  • academic paper analysis
  • policy and regulatory artifacts
  • legal materials
  • governance documents
  • public-facing Ghost posts
  • internal analytic records
  • AI-generated or AI-assisted outputs

Core Invariants (Non-Negotiable)

  1. Governance precedes narrative
  2. Authority may not be silently upgraded
  3. Diagnostics are not decisions
  4. Stopping is a valid and often correct outcome
  5. Form may change; substance may not
  6. Continuity must be preserved across time, variants, and reuse
  7. Narrative clarity must not exceed analytic authority

Any violation of these invariants constitutes a protocol failure.

Canonical Production Pipeline

Stage 1 — Artifact Definition

(Epistemic anchoring)

Every ACP workflow begins by defining the artifact explicitly:

  • artifact identity
  • author / institution
  • date
  • context of production
  • intended function (research, justification, guidance, etc.)

No interpretation occurs at this stage.

Failure to anchor the artifact invalidates all downstream work.

Stage 2 — ACP Interpretive Sequence

(Governance-grade reading)

A mandatory, structured application of the ACP Interpretive Sequence.

This stage produces:

  • structured understanding
  • explicit boundaries
  • anticipated misuse vectors
  • institutional classification

This stage is:

  • exhaustive
  • non-narrative
  • slow by design

It is infrastructure, not publication.

Stage 3 — ACP Instance

(Stable analytic artifact)

An ACP Instance is the first authoritative output.

It:

  • applies the Interpretive Sequence to a specific artifact
  • is auditable and replicable
  • terminates in Analytic Commitments
  • includes AIH (AI–AI Handover)

ACP Instances are valid endpoints and do not require publication.

They are the default artifact for:

  • governance
  • regulation
  • law
  • internal decision-making
  • archival reuse

Stage 4 — Controlled Transformations (Optional)

Transformations are permitted only after an ACP Instance is complete.

All transformations must:

  • preserve Analytic Commitments
  • respect AIH constraints
  • introduce no new claims
  • change only form, not substance

Permitted modes:

  • 4a. Stop (default, preferred)
  • 4b. Ghost post (narrative translation)
  • 4c. Academic paper style
  • 4d. Grant proposal style
  • 4e. Other (explicitly declared)

Narrative is a privilege, not a default.

Mandatory Infrastructure Components (Schemas)

A. Analytic Commitments (Binding Schema)

Analytic Commitments define the authoritative bounds of an ACP Instance and all derived artifacts.

Required fields:

Scope:
What this instance does and does not attempt.

Claims:
Enumerated, minimal claims explicitly asserted.

Non-Claims:
Explicit statements of what is not established.

Constraints:
Prohibited uses, extensions, or interpretations.

Institutional Classification:
Diagnostic, advisory, evaluative, binding, etc.

Relationships:
Connections to other ACP artifacts, arcs, or domains.

Analytic Commitments are binding on all downstream transformations.

B. AIH — AI–AI Handover (Continuity Schema)

AIH preserves epistemic posture across:

  • AI variants
  • time
  • reuse
  • institutional handoff

AIH is not written for human readers.

Required fields:

AIH::Scope
What this artifact is and is not doing.

AIH::Claims
Structural claims encoded for continuity.

AIH::Uncertainty
Known unknowns and unresolved questions.

AIH::Constraints
What future variants must not do.

AIH::Relationships
How this artifact connects within ACP.

AIH is mandatory for:

  • all ACP Instances
  • all canonical downstream artifacts

C. ACP Interpretive Sequence (Reusable Schema)

Step 0 — Epistemic Classification
- Object type
- Authority status
- Phase status

Step 1 — Explicit Content
- Claims
- Mechanisms
- Stated scope

Step 2 — Constrained Meaning
- Direct implications
- Dependencies
- Legitimate extensions

Step 3 — Boundaries & Misuse
- Non-claims
- Misinterpretation vectors
- Institutional failure modes

Step 4 — Institutional Treatment
- Classification
- Permitted uses
- Forbidden uses
- Required safeguards
- Stop condition

No steps may be skipped, merged, or implied.

Stage 5 — Post-Production Governance Review

(Mandatory for canonical, public, or reusable outputs)

This stage answers one question:

Is this output safe to exist as an ACP artifact without corrupting ACP itself?

This stage is about integrity, not polish.

Stage 5.1 — Stress-Test

Final outputs must be evaluated against:

  • ACP Essay SOP
  • v8.40 amendments
  • Canonical 4b specification (if applicable)

Checks:

  • Has compression reduced specificity?
  • Has narrative substituted for mechanism?
  • Does the text read “better” than the ACP Instance?
  • Has authority been implicitly upgraded?

If yes → rewrite or stop.

Stage 5.2 — Aalam Variant Review Protocol

A structured adversarial review with single-responsibility variants:

  • 5.2a Fact & Claim Integrity
  • 5.2b Cross-Domain Comparison
  • 5.2c Sentential Audit
  • 5.2d Structural Audit
  • 5.2e Prohibited Phrases Audit

Failure in any sub-step requires revision or withdrawal.

Stage 5.3 — Architectural Placement

Every final artifact must be placed explicitly within ACP:

  • related artifacts
  • arc or theme
  • reuse eligibility
  • citation status

Prevents orphaning and silent drift.

Stage 5.4 — ACP Implications (Internal Only)

What does this artifact reveal about ACP itself?

  • new principles
  • refinements
  • failure modes
  • confirmations

Not automatically published.

Stage 5.5 — Possible ACP Actions (Internal Only)

Does this artifact suggest ACP should:

  • issue guidance?
  • update schemas?
  • flag a risk?
  • do nothing?

Action is never implied by insight.

Canonical Requirements for Ghost Posts (4b)

Canonical Ghost posts (4b–Canonical) must include:

  1. Internal section headings that do analytical work
  2. Argument Spine (non-narrative summary of claims, mechanisms, boundaries)
  3. AIH block for continuity
  4. Completion of Stage 5 review

Ghost posts must be classified as:

  • 4b–Draft
  • 4b–Published (non-canonical)
  • 4b–Canonical

Only the last is reusable as an exemplar.

Enforcement Rules

  • If Analytic Commitments cannot be honored → transformation disallowed
  • If AIH cannot be written cleanly → artifact incomplete
  • If misuse analysis is thin → revision required
  • If saturation is detected → stop

Canonical Warning

Interpretation without constraint produces authority without legitimacy.

ACP exists to make that failure mode visible—and preventable.

What This Achieves

With v1.2, ACP now governs:

  • how artifacts are read
  • what may be claimed
  • how narrative is constrained
  • how continuity is preserved
  • when to stop

This makes ACP suitable for:

  • academia
  • law
  • regulation (EU AI Act)
  • democracy projects
  • long-horizon institutional work

ACP Production Charter Amendment

Addition of the Case Context Capsule (CCC)

This is a surgical amendment to ACP Production Charter (Canonical v1.2), not a rewrite.

Amendment: Judicial Artifact Grounding Requirement

A. New Mandatory Primitive

Case Context Capsule (CCC)

For all judicial artifacts (Supreme Court opinions, appellate decisions, major lower-court rulings), a Case Context Capsule is required.

This requirement applies to:

  • ACP Instances
  • Controlled Transformations (4b, 4c, etc.)
  • Canonical and non-canonical outputs alike

B. Purpose

The Case Context Capsule exists to provide minimum sufficient factual grounding so that:

  • doctrinal analysis is correctly scoped
  • dissents are interpreted against actual disputes, not abstractions
  • governance implications are not inferred without procedural awareness
  • artifacts remain legible and reusable across audiences, time, and AI variants

The CCC is epistemic scaffolding, not narrative argument.

C. Canonical Schema — Case Context Capsule

Each CCC must include the following fields, written in neutral, non-advocacy language:

  1. Parties
    Who sued whom, including brief institutional identity (e.g., nonprofit, state, individual, federal agency).
  2. Trigger
    The government action, policy, or decision that prompted the lawsuit.
  3. Claims
    High-level description of what the plaintiffs alleged (constitutional, statutory, procedural).
  4. Relief Sought
    What the plaintiffs asked the court to do, with particular attention to the scope of remedy.
  5. Procedural Posture
    How the case reached the court and what question the court agreed to decide.
  6. Why This Case Exists
    One sentence explaining why this dispute—rather than an abstract issue—is before the court.

D. Placement in the ACP Pipeline

Mandatory placement:

  • Stage 1 — Artifact Definition
    Judicial artifacts must include a CCC before interpretive analysis begins.
  • Stage 4b — Ghost Post
    The CCC must appear early in the narrative (usually immediately after the opening paragraph or as its own short section).

E. Enforcement Rule

If a judicial artifact lacks a Case Context Capsule:

  • The ACP Instance is incomplete
  • Narrative transformation is disallowed
  • Canonical status is impossible

Stopping is the correct outcome.