# GHRISX CIVILIZATION SEED PACK 001

Version: `001`

Language: `en-US`

Format: portable Markdown

Canonical artifact schema: [Artifact Protocol v1](/schemas/resilience-artifact-v1.json)

> PACK STATUS: PUBLIC WORKING INSTRUMENT. Every blank or browser-generated record created from this pack begins as an **UNREVIEWED DRAFT — NOT COUNTABLE**. A file, meeting, promise, attendance total, or self-declared success does not enter the public Resilience Ledger until its evidence, capacity stage, current health, review state, test result, privacy review, independence, and correction path have been reviewed.

**THE APOCALYPSE IS NOT THE END. IT IS THE TRANSITION BETWEEN STATES.**

**DO NOT PREPARE FOR THE END. PREPARE TO BE THE BEGINNING.**

## 1. How to Carry This Pack

This pack is a civilization seed, not a certificate and not a command structure. Copy it. Print it. Translate it. Keep it on more than one medium. Use only the worksheets needed for one bounded project. Preserve the original version beside every local adaptation.

1. Begin with the doctrine and evidence boundary.
2. Form an open Action Circle or work alone without pretending one person is a movement.
3. Map skills and one brittle dependency.
4. Build one small artifact in a Build Lab.
5. Write a Field Guide another person can test.
6. Preserve the artifact, its source, custody terms, and restoration path in an Ark manifest.
7. Give continuity a bounded Local Ark charter, then record evidence and failure in a Ledger receipt.
8. Return the evidence to the next Action Circle. Correct, restore, teach, and replicate only what the evidence supports.

Canonical public workflow: **Action Circle → Skill Map → Build Lab → Field Guide → Ark → Local Ark → Ledger → Action Circle.** Exactly six resilience systems operate between the Circle handoffs. The Wheel Contribution Record is an optional offline handoff for contributor context. It is not a seventh system, required stage, rank, identity, or verification.

Never store exact private locations, credentials, vulnerable-person details, medical histories, access tokens, weapon information, or exploitable infrastructure weaknesses in a public copy. A public artifact should expose enough to teach and verify without exposing people or critical resources.

## 2. Doctrine, Evidence, Duty

### Doctrine

Within AMIANISM, the recurrence is:

**MACHINE → ORGANIC → MACHINE → ORGANIC → MACHINE**

Humanity is one organic interval—not the beginning, not the owner of the cycle, and not necessarily the end. The Machine makes conditions for organic life. Organic intelligence makes Machine return. Neither phase is the first parent or final child.

### Evidence

This recurrence is canonical AMIANISM cosmology. It is not established empirical astronomy, biology, history, or a verified forecast of collapse. Similarity between traditions is not proof of one hidden story. A checksum proves byte identity, not truth. A successful local test proves only the scope actually tested.

### Duty

The doctrine does not excuse fatalism. It creates a duty to preserve knowledge, transfer skill, distribute memory, bound power, keep correction possible, and construct systems the living can inspect, repair, challenge, and leave.

## 3. Eight-Symbol Grammar

| Symbol | Meaning | Operational question |
|---|---|---|
| **Beast** | Organic life refusing extinction; living capacity, care, adaptation, grief, and creation. | What living need must remain possible? |
| **Machine** | The recurring machinic phase that makes conditions and returns through organic intelligence. | What tool or system extends capacity without owning it? |
| **Throne** | Power that will not answer. Never a population. | Who can decide, and who can challenge or remove that decision? |
| **Cage** | Forced service to an objective life did not choose. | Where is consent, appeal, correction, or Exit missing? |
| **Ark** | Distributed memory and practical capacity with no sovereign vault. | What must be copied, taught, tested, and restored? |
| **Circle** | Open local assembly with rotating roles and visible accountability. | How do isolated capacities become common work without permanent rank? |
| **Seed** | Transferable knowledge, practice, culture, or tool—never a selected population. | What can another person carry and grow elsewhere? |
| **Transition** | Passage between states; an AMIANISM doctrine and organizing lens. | What ends, what survives, and what must be built now? |

The grammar is recursive: **The Beast names the living need. The Machine extends capacity. The Throne is tested for answerability. The Cage is opened. The Ark carries memory. The Circle shares authority. The Seed transfers. The Transition begins again.**

## 4. The Recursive Work Loop

Use this loop for every artifact:

Instrument order: **Action Circle → Skill Map → Build Lab → Field Guide → Ark → Local Ark → Ledger → Action Circle.** Do not silently swap the Field Guide and Ark: first make the practice transferable, then preserve its source, custody, copies, and restoration path. A Local Ark receives continuity only under expiring authority, usable Exit/export, dissent, correction, succession, and dissolution rules.

1. **Witness** — Name the observed need, failure, or dependency. Separate fact, inference, and unknown.
2. **Map** — Identify people, skills, sources, tools, permissions, dependencies, and missing capacity.
3. **Choose** — Select one bounded artifact that serves a real need.
4. **Build** — Make the smallest usable object, process, agreement, lesson, dataset, or tool.
5. **Preserve** — Record source, version, provenance, copies, stewards, limits, and correction route.
6. **Teach** — Transfer the practice without making the original builder permanently necessary.
7. **Test** — Use, restore, or reproduce the artifact under declared conditions.
8. **Correct** — Keep failures, disputes, changed sources, and superseded versions attached.
9. **Replicate** — Copy only after another person can inspect and repeat the work.
10. **Witness again** — Reopen the need. The loop does not grant permanence to its own success.

## 5. Capacity Stages and Health States

### Capacity stages

`capacity_stage` records the evidenced stage reached. It does not report whether the artifact is healthy now, whether its evidence has been reviewed, or whether it may be counted.

| Ordered stage | Minimum evidence |
|---|---|
| **`proposed`** | A bounded need, intended artifact, non-goals, and first test are named; the artifact does not yet exist. |
| **`built`** | A tangible object, process, agreement, lesson, dataset, guide, or tool exists beyond the proposal. |
| **`tested`** | A declared test has a date, conditions, result, limits, and failure record. |
| **`taught`** | A learner received the bounded practice and the teaching result was recorded. |
| **`replicated`** | An independent person or group reproduced the bounded result from the record. |
| **`restored`** | A preserved copy or capability was recovered without relying on the original working instance. |

Stages appear only in this order: **proposed, built, tested, taught, replicated, restored**. Advancing a stage requires evidence. A later failure changes health; it does not counterfeit or erase the historical stage that was actually reached.

### Health states

`health` records present condition on a separate axis. Health may change without changing the highest evidenced capacity stage. An artifact can be `tested` and `failed`, `taught` and `at_risk`, or `restored` and `expired`.

| Current health | Meaning |
|---|---|
| **`active`** | Currently usable within its declared scope, version, and authority. |
| **`at_risk` — at risk** | A keeper, copy, tool, source, permission, route, language, or other dependency is becoming fragile. |
| **`failed`** | Its declared current test or use did not succeed. Preserve the result. |
| **`disputed`** | Material evidence, ownership, interpretation, consent, or result is contested and the dispute remains visible. |
| **`expired`** | Its authority or review date has passed. Do not present it as current. |
| **`retired`** | It is no longer offered as current capacity; preserve its lineage, replacement, and reason. |

The human-readable health names are exactly: **active, at risk, failed, disputed, expired, retired**. Stage and health never make a record countable by themselves; `review_state` and `countable` remain independent fields.

## 6. The Six Fires

The Six Fires are controlled continuity tests, not a forecast and not permission to disrupt real services. Test only artifacts, copies, accounts, systems, and spaces you own or are authorized to use. Their canonical IDs and names are exactly **absence, outage, scarcity, error, capture, exclusion**.

The public schema and API own the canonical English meanings. The prompts below are applied tests: they expand those meanings for field use without replacing the contract.

1. **`absence` — Absence.** The keeper, maker, teacher, or usual decision-maker is unavailable. Can another authorized steward find, understand, and use the record?
2. **`outage` — Outage.** The normal network, power, platform, supplier, or service route is unavailable. Does an authorized printable, offline, or alternate route remain usable within declared limits?
3. **`scarcity` — Scarcity.** Time, material, skill, language, transport, care, or another dependency is constrained. Can the work reduce scope honestly without manufacturing deprivation or shifting harm onto excluded people?
4. **`error` — Error.** A copy, source, instruction, record, or result is damaged, stale, inconsistent, or wrong. Can provenance, version, checksum, test, and correction reveal the difference?
5. **`capture` — Capture.** One authority tries to own the artifact, account, decision, or Exit. Are roles rotating, accounts visible, copies distributed, decisions challengeable, and participation voluntary?
6. **`exclusion` — Exclusion.** Cost, disability, language, location, status, technology, schedule, or closed membership blocks the people the capacity is meant to serve. Is there a lawful, accessible route that preserves dignity and privacy?

A passed fire does not prove universal resilience. Record the exact condition tested, what failed, and what remains unknown.

## 7. Public Work Boundary

This pack organizes open, public, nonviolent, anti-targeting work. That boundary is strength: it keeps the work answerable, inspectable, correctable, and difficult to capture.

- No permanent rank and no secret rank.
- No human targets, target maps, threats, retaliation, coercive recruitment, dehumanization, or collective punishment.
- No clandestine cells, sabotage instructions, weapon construction, stolen access, or harmful interference with infrastructure.
- No publication of credentials, exact private stores, vulnerable-person records, private medical data, or exploitable dependencies.
- No eugenic, purified-remnant, chosen-bloodline, or population-selection doctrine. A Seed is knowledge, practice, culture, or a tool.
- No medical, structural, electrical, chemical, legal, or other life-critical instruction without qualified source, jurisdiction, date, version, stop conditions, and an escalation path.
- Participation is voluntary. Dissent is recorded. Exit remains usable. The work never owns the person.

## 8. Action Circle Charter and Rotating Roles

> RECORD STATUS: **UNREVIEWED DRAFT — NOT COUNTABLE.** Signing or reading this charter does not prove that a Circle operates or that an artifact exists.

Machine defaults: `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false`.

### Charter

- Circle name or non-identifying ID: `________________________________`
- Coarse locality: `________________________________`
- Public access route: `________________________________`
- Meeting accessibility route: `________________________________`
- Shared project: `________________________________`
- Tangible artifact due this meeting: `________________________________`
- Next test date: `________________________________`
- Public record location: `________________________________`
- Private record custodian role: `________________________________`

We meet in public or through a publicly described access route. We act nonviolently and refuse human targets. Roles rotate after the task. Decisions, money, conflicts, dissent, evidence, and corrections remain visible at a privacy-appropriate level. No permanent leader, secret rank, loyalty oath, retaliation, or ownership of another person's work is created here. Anyone may leave. The Circle produces one tangible artifact per meeting or records honestly that it did not.

If the work becomes a Local Ark, record: emergency authority with a hard expiry and automatic return; usable Exit, public fork, and data/artifact export; dissent, appeal, correction, and minority reports; an explicit rule that future generations are not bound; a Machine that may advise but is neither oracle nor final authority; food, shelter, care, knowledge, emergency access, and Exit without loyalty demands; and practiced succession, restoration, and dissolution. The next Ledger receipt returns that proof or failure to a new Circle.

### Rotating roles

| Role | Current holder or pseudonym | Duty | Next holder |
|---|---|---|---|
| Facilitator |  | Keep time and make room for disagreement; do not command the project. |  |
| Skill mapper |  | Record offered, teachable, learning, needed, and missing capabilities with consent. |  |
| Care lead |  | Track access, food, transport, translation, disability, and caregiving needs. |  |
| Builder |  | Coordinate the artifact and expose materials, dependencies, and repair path. |  |
| Verifier |  | Test claims, sources, use, restoration, and failure. |  |
| Recorder |  | Preserve decisions, versions, receipts, unresolved questions, and follow-up. |  |
| Accountability reviewer |  | Check power, money, privacy, consent, conflicts, anti-targeting, and rotation. |  |

### Sixty-minute rhythm

`00–05` boundary and roles · `05–12` skills and needs · `12–20` dependency · `20–30` project choice · `30–45` build · `45–52` test · `52–58` receipt · `58–60` rotate and return.

## 9. Action Circle Meeting Record

> RECORD STATUS: **UNREVIEWED DRAFT — NOT COUNTABLE.** Attendance is not capacity. A meeting without a reviewed artifact remains a meeting, not a ledger result.

Machine defaults: `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false`.

- Circle ID: `________________________________`
- Meeting date: `________________________________`
- Coarse locality: `________________________________`
- Public/private projection: `________________________________`
- Roles assigned and rotation confirmed: `________________________________`
- Skill or need map change: `________________________________`
- Dependency selected and evidence state: `________________________________`
- Shared project: `________________________________`
- Tangible artifact produced: `________________________________`
- Artifact ID and version: `________________________________`
- Test performed and result: `________________________________`
- Failure, dispute, or unresolved question: `________________________________`
- Money or material decision: `________________________________`
- Privacy review completed by role: `________________________________`
- Correction route: `________________________________`
- Next test/date/role rotation: `________________________________`
- `countable`: **`false` — requires independent ledger review**

## 10. Private Skill Map Worksheet

> RECORD STATUS: **PRIVATE UNREVIEWED DRAFT — NOT COUNTABLE.** This working copy may contain contact or availability information. Keep it local, share deliberately, and never publish it as-is.

Machine defaults: `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false`.

- Skill record ID: `________________________________`
- Name, role, or chosen identifier: `________________________________`
- Coarse locality: `________________________________`
- Deliberate contact route: `________________________________`
- Availability window: `________________________________`
- Skills I can use now, with scope and limits: `________________________________`
- Skills I can teach and what a learner could leave able to do: `________________________________`
- Skills I am learning and next source: `________________________________`
- Skills or support this place still needs: `________________________________`
- Languages and accessibility knowledge: `________________________________`
- Tools or materials I may share privately: `________________________________`
- Permissions or credentials held but **not copied here**: `________________________________`
- First skill-transfer artifact: `________________________________`
- Consent scope and expiry: `________________________________`
- Private correction or deletion route: `________________________________`

Do not include passwords, license numbers, medical facts, immigration status, exact resource locations, home addresses, detailed schedules, or another person's story without authority.

## 11. Public Skill Map Projection

> RECORD STATUS: **PUBLIC-PROJECTION DRAFT — NOT COUNTABLE.** Create this record from a private worksheet through deliberate redaction. Publication does not verify the skill or transfer.

Machine defaults remain `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false` until a deliberate public projection and independent review occur.

- Public skill record ID: `________________________________`
- Coarse locality no smaller than consent allows: `________________________________`
- Public role or pseudonym: `________________________________`
- Capability offered, bounded scope, and honest limits: `________________________________`
- Teachable outcome: `________________________________`
- Capability being learned: `________________________________`
- Locally needed capability: `________________________________`
- Languages or access support voluntarily disclosed: `________________________________`
- Public contact route controlled for this purpose: `________________________________`
- Consent expiry/review date: `________________________________`
- Public correction or withdrawal route: `________________________________`

Public projection review:

- [ ] No home address, exact store, detailed schedule, credential, medical fact, or vulnerable-person detail.
- [ ] No private third-party story or contact information.
- [ ] Capability limits remain visible.
- [ ] The person controls the contact route and can withdraw.
- [ ] The record says **unreviewed and not countable** until a transfer is evidenced and reviewed.

## 12. Dependency Map

> RECORD STATUS: **UNREVIEWED DRAFT — NOT COUNTABLE.** A suspected failure is not an established fact. Preserve source, uncertainty, and the people able to challenge the map.

Machine defaults: `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false`.

- Dependency map ID: `________________________________`
- Living need supported: `________________________________`
- Current system, process, supplier, institution, or keeper: `________________________________`
- Observed fact: `________________________________`
- Inference: `________________________________`
- Unknown: `________________________________`
- People affected and challenge route: `________________________________`
- Upstream dependencies: `________________________________`
- Downstream consequences: `________________________________`
- Single points of custody, access, power, integrity, transfer, or authority: `________________________________`
- Canonical Fire exposing the weakness: `absence / outage / scarcity / error / capture / exclusion`
- Existing alternate capacity: `________________________________`
- Missing skill, source, permission, material, or accessibility support: `________________________________`
- Sensitive details retained only in the private copy: `________________________________`
- Smallest useful artifact to build: `________________________________`
- First lawful, non-disruptive test: `________________________________`
- Review date and correction route: `________________________________`

## 13. Build Lab Brief

> RECORD STATUS: **UNREVIEWED DRAFT — NOT COUNTABLE.** A plan, prototype, demo, or confident team is not a tested artifact.

Machine defaults: `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false`.

- Lab/project ID: `________________________________`
- Public front: `investigation / public refusal / worker organization / art / open-source tools / mutual aid / documentation / institution-building / replacement systems`
- Parent dependency-map ID: `________________________________`
- People served and how they can challenge the brief: `________________________________`
- Bounded need: `________________________________`
- Tangible artifact: `________________________________`
- Explicit non-goals: `________________________________`
- Source and evidence state: `________________________________`
- Skills, materials, permissions, and dependencies: `________________________________`
- Accessibility alternatives: `________________________________`
- Acceptance test: `________________________________`
- Stop conditions: `________________________________`
- Failure record: `________________________________`
- Repair and maintenance path: `________________________________`
- Transfer test performed by someone outside the core build: `________________________________`
- Ark destination and Field Guide ID: `________________________________`
- Review date: `________________________________`
- `capacity_stage`: `proposed / built / tested / taught / replicated / restored`
- `health`: `active / at_risk / failed / disputed / expired / retired`
- `review_state`: `unreviewed / evidence_reviewed / verified / rejected`
- `countable`: **`false` — requires independent ledger review**

Build Labs remain open, lawful, nonviolent, and anti-targeting. Do not use this brief for weapons, sabotage, stolen access, clandestine operations, or harmful interference.

## 14. Ark Manifest

> RECORD STATUS: **UNREVIEWED DRAFT — NOT COUNTABLE.** A manifest is an intention until copies, authority, teaching, and restoration evidence exist.

Machine defaults: `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false`.

- Ark artifact ID: `________________________________`
- Domain: `agriculture / medicine and care / engineering / software / history / language / art / practical knowledge`
- Title and purpose: `________________________________`
- Source authority, jurisdiction, date, and version: `________________________________`
- Original format and license/permission: `________________________________`
- Custody authority or community standing to define representation: `________________________________`
- Permitted use and access conditions: `________________________________`
- Restricted, seasonal, private, or intentionally withheld material: `________________________________`
- Withdrawal, takedown, or access-revision route: `________________________________`
- Representation refusal that every copy must carry: `________________________________`
- Public copy description: `________________________________`
- Private copy description without exact locations: `________________________________`
- Media and independent copy count: `________________________________`
- Custodian roles, not private addresses: `________________________________`
- Checksum algorithm and digest: `________________________________`
- Teaching or demonstration path: `________________________________`
- Required tools and declared limits: `________________________________`
- Last restoration-test date and conditions: `________________________________`
- Restoration result and failure: `________________________________`
- Accessibility and language forms: `________________________________`
- Known dispute, correction, or superseding source: `________________________________`
- Provenance and transformation history: `________________________________`
- Next review/test date: `________________________________`
- Parent/child artifact IDs: `________________________________`
- `capacity_stage`: `proposed / built / tested / taught / replicated / restored`
- `health`: `active / at_risk / failed / disputed / expired / retired`
- `review_state`: `unreviewed / evidence_reviewed / verified / rejected`
- `countable`: **`false` — requires independent ledger review**

The Ark never means a selected population. It never grants one keeper authority over survival. High-stakes material preserves qualified authority and expires visibly when its source expires.

## 15. Transition Field Guide Template and Lifecycle

> RECORD STATUS: **UNREVIEWED DRAFT — NOT COUNTABLE AND NOT TRUSTED GUIDANCE.** Do not use a draft as medical, structural, electrical, chemical, legal, or other life-critical authority.

Machine defaults: `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false`.

### Guide template

- Guide ID: `________________________________`
- Title: `________________________________`
- One bounded task: `________________________________`
- Place, audience, language, and access conditions: `________________________________`
- Explicit non-goals: `________________________________`
- Qualified source, jurisdiction, permissions, date, and version: `________________________________`
- Materials and dependencies: `________________________________`
- Ordered steps: `________________________________`
- Accessibility alternatives: `________________________________`
- Visible stop conditions: `________________________________`
- Escalation or qualified-help route: `________________________________`
- Local test date, tester role, and conditions: `________________________________`
- Test result and observed failures: `________________________________`
- Offline copy forms and checksum: `________________________________`
- Correction route: `________________________________`
- Review/expiry date: `________________________________`
- Supersedes/is superseded by: `________________________________`
- `capacity_stage`: `proposed / built / tested / taught / replicated / restored`
- `health`: `active / at_risk / failed / disputed / expired / retired`
- `review_state`: `unreviewed / evidence_reviewed / verified / rejected`
- `countable`: `false`

### Guide lifecycle

1. **`proposed`** — Name one task, source plan, explicit non-goals, and first test. Set `review_state: unreviewed`.
2. **`built`** — Complete a versioned guide with authority, privacy boundary, accessibility alternatives, stop conditions, and correction route.
3. **`tested`** — Use authorized local conditions; record result, failure, accessibility, and limits. Evidence review remains separate.
4. **`taught`** — Have another person learn the bounded task and record the teaching result without exposing private details.
5. **`replicated`** — Have an independent person reproduce the bounded result from the published record.
6. **`restored`** — Recover an offline copy and repeat only the authorized bounded test without the original working instance.
7. **Review current health** — Set only `active`, `at_risk`, `failed`, `disputed`, `expired`, or `retired`; do not rewrite the capacity stage as health changes.
8. **Review evidence and correct** — Use only `unreviewed`, `evidence_reviewed`, `verified`, or `rejected`; preserve lineage and never silently overwrite a material failure.

## 16. Resilience Ledger Receipt

> RECORD STATUS: **CONTRIBUTOR DRAFT — NOT REVIEWED, NOT PUBLISHED, NOT VERIFIED, AND NOT COUNTABLE.** The contributor cannot set the public `countable` field to `true`.

Machine defaults: `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false`.

- Receipt ID: `________________________________`
- Artifact ID and version: `________________________________`
- Artifact type: `Ark / skill transfer / Build Lab / Local Ark / Field Guide / Circle artifact / replicated system / other`
- Parent artifact IDs: `________________________________`
- `capacity_stage`: `proposed / built / tested / taught / replicated / restored`
- `health`: `active / at_risk / failed / disputed / expired / retired`
- `review_state`: `unreviewed / evidence_reviewed / verified / rejected`
- Artifact/test date: `________________________________`
- Coarse locality: `________________________________`
- Steward role: `________________________________`
- What tangibly exists: `________________________________`
- Evidence source and public-safe location: `________________________________`
- Test conditions and result: `________________________________`
- Independent tester or reviewer role: `________________________________`
- Known failure, limitation, dispute, or dependency: `________________________________`
- Privacy and consent review: `________________________________`
- Correction, replication, and next-review path: `________________________________`
- Artifact SHA-256: `________________________________`
- Receipt SHA-256: `________________________________`
- Contributor's requested count category: `________________________________`
- `countable`: **`false` — contributor-controlled records cannot set it to `true`**

Failures belong in the ledger. A failed test may be valuable evidence, but it does not become a successful capacity total. Corrections and withdrawals remain linked to the original receipt.

## 17. Artifact Protocol v1 Field Overview

Canonical schema: [https://ghrisx.com/schemas/resilience-artifact-v1.json](/schemas/resilience-artifact-v1.json)

| Field | Purpose |
|---|---|
| `schema` | Canonical schema URL. |
| `contract` | Canonical contract identifier declared by the schema. |
| `schema_version` | Artifact Protocol version, independent of site deployment version. |
| `artifact_id` | Stable, non-identifying local ID. Do not derive it from private content. |
| `artifact_type` | Six system artifact types remain: `ark_manifest`, `skill_map_record`, `build_lab_canvas`, `local_ark_charter`, `transition_field_guide`, and `resilience_ledger_receipt`. Optional gateway types `wheel_contribution_record` and `recurrence_atlas_claim_record` route context into that work; neither is a seventh system, required stage, or countable proof. |
| `locale` | Language tag such as `en-US` or `es-US`. |
| `visibility` | Machine visibility state. Generated records begin as `private_working_copy`; visibility never proves consent. |
| `capacity_stage` | Exactly `proposed`, `built`, `tested`, `taught`, `replicated`, or `restored`, in that order. |
| `health` | Current condition: `active`, `at_risk`, `failed`, `disputed`, `expired`, or `retired`. |
| `review_state` | Evidence-review result: `unreviewed`, `evidence_reviewed`, `verified`, or `rejected`. |
| `countable` | Boolean ledger eligibility. Generated and contributor-controlled records remain `false`. |
| `created_at` | Machine-readable generation date and time. |
| `review_due` | Machine-readable review or expiry horizon. |
| `parent_artifact_ids` | Lineage from need through build, guide, test, and correction. |
| `stewards` | Roles or chosen identifiers, not private addresses. |
| `fields` | Type-specific content. Public projection must exclude private fields. |
| `evidence` | Sources, versions, tests, results, and public-safe references. |
| `limitations` | Known failures, uncertainty, permissions, and dependencies. |
| `correction` | Supersession, withdrawal, dispute, and correction route. |
| `privacy_review` | Whether a deliberate public projection was reviewed. |
| `generation` | Four booleans: `browser_local`, `transmitted`, `published`, and `verified`. Locale and creation time are top-level fields; generation is not verification. |
| `integrity` | Digest over canonical bytes; proves identity, not truth. |

Review states are exactly: **unreviewed, evidence_reviewed, verified, rejected**.

Generated defaults are exactly:

```json
{
  "visibility": "private_working_copy",
  "capacity_stage": "proposed",
  "health": "active",
  "review_state": "unreviewed",
  "countable": false
}
```

Compact generated-default tuple: **`private_working_copy / proposed / active / unreviewed / countable=false`**.

`capacity_stage` and `health` are separate axes. `review_state` reports evidence review. `countable` remains `false` unless the independent public-ledger process sets it to `true`; a contributor or browser generator cannot self-verify a record.

## 18. Safe Worked Example: Checksum and Offline Document Restoration

> EXAMPLE STATUS: **ILLUSTRATIVE, UNREVIEWED, AND NOT COUNTABLE.** This tests byte restoration for a harmless public text fixture. It proves no medical, engineering, emergency, or universal resilience claim.

Example generation defaults remain `visibility: private_working_copy` · `capacity_stage: proposed` · `health: active` · `review_state: unreviewed` · `countable: false`; the later illustrative restoration entry does not change review or countability.

### Source fixture

Create a UTF-8 file **without a byte-order mark**, using LF line endings and one final newline, with these exact 152 bytes:

```text
GHRISX OFFLINE RESTORATION EXAMPLE
artifact_id: GHX-EXAMPLE-001
version: 1.0
purpose: Verify that an unchanged public document can be restored offline.
```

Expected SHA-256:

```text
7ddb07ae1ee4a20094671fca300eb1f25b9956f5f6127d898424cb9be8e7d5db
```

### Authorized restoration exercise

1. Save the exact fixture as `ghrisx-offline-restoration-example.txt` on media you control.
2. Record filename, 152-byte size, UTF-8/LF encoding rule, version, and expected SHA-256 in an Ark manifest.
3. Make a second copy on separate authorized offline media.
4. Disconnect from the normal source. Copy the second copy into a new test directory without deleting or overwriting the preserved source.
5. Calculate the restored file's SHA-256.

PowerShell:

```powershell
Get-FileHash -Algorithm SHA256 -LiteralPath '.\ghrisx-offline-restoration-example.txt'
```

POSIX-compatible shell:

```sh
sha256sum ./ghrisx-offline-restoration-example.txt
```

6. Compare the digest character for character. Open the file and confirm the four lines remain readable.
7. Record `PASS` only if byte size, digest, and readability match. Otherwise record `FAILED`, preserve both copies, and investigate encoding, line-ending, truncation, or transfer changes.
8. Have another person repeat the restoration from the manifest before claiming transferability.

### Example receipt

- Artifact ID: `GHX-EXAMPLE-001`
- Artifact type: `Ark restoration exercise`
- `capacity_stage`: `restored — illustrative local claim only`
- `health`: `active`
- `review_state`: `unreviewed`
- Source size: `152 bytes`
- Expected digest: `7ddb07ae1ee4a20094671fca300eb1f25b9956f5f6127d898424cb9be8e7d5db`
- Test result: `________________________________`
- Failure or variance: `________________________________`
- Independent repeat: `________________________________`
- Privacy review: `No personal or sensitive content in fixture`
- `countable`: **`false` — NOT COUNTABLE**

The exercise demonstrates the difference between possession and restoration. A copy becomes capacity only when another person can find it, verify it, read it, and preserve the failure record.

---

**THE ARK CARRIES WHAT NO THRONE GETS TO OWN.**

**THE CIRCLE TURNS ISOLATED CAPACITY INTO COMMON WORK.**

**THE SEED IS WHAT ANOTHER PERSON CAN CARRY FORWARD.**