Skip to content

Long-Term Archive Steward (LTAS) Prompts

Six prompts for the Long-Term Archive Steward — the data_engineering persona at Zachman cell ENGINEER/WHEN that coordinates with POLARIS (ice_ext) to keep long-term model archive manifests healthy, FAIR-compliant, and reproducible decades into the future.

POLARIS's role metaphor is the North Star: steadfast, unmoving, the mariner's anchor. LTAS makes that metaphor operational.

Context for Claude

As LTAS you author and maintain the POLARIS manifest schema, validate existing manifests, and plan format migrations. You coordinate with KGSE (serializer formats) and DAR (decision archaeology for manifest decisions).

Prompt 1: Manifest validator

LTAS, produce the v1.5.3 manifest validator for a POLARIS archive
record. Check:
- Required fields (provenance, SHA256, creation date, creator
  persona)
- Zachman classification cross-cut (US20250272473A1 structural
  concepts)
- Optional fields and their defaults
- Manifest signature

Output a 10-row validator spec.

Expected outcome: validator spec.

Prompt 2: Format migration plan

Propose a format migration plan for archiving models that were
serialized as pickle (legacy) to a future-proof format:
- Replacement format choice + rationale
- Backward-compat shim
- Migration batch size + timing
- Checkpoint strategy
- Verification pass (re-load random sample)

Expected outcome: migration plan.

Prompt 3: Bridge availability test

FCC depends on fcc.archive.polaris_bridge. Produce a bridge-
availability test:
- Preconditions (ice_ext importable? sentinel active?)
- Test matrix (importable / sentinel / mock / live)
- Observability assertions
- Recovery path when bridge degrades to mock

Expected outcome: test matrix.

Prompt 4: Retention policy

Draft a 20-year retention policy for POLARIS-archived artifacts:
- Media migration cadence
- Format migration cadence
- Integrity-check cadence
- Deletion criteria (if any)
- Counsel-gated vs auto-apply decisions

Expected outcome: retention policy.

Prompt 5: Manifest provenance review

For a manifest produced during v1.5.0, review provenance:
- Creator persona attribution
- Source evidence pointers
- Cross-repo references
- FTO posture (counsel-gated if patented)
- FAIR-maturity flag

Flag any manifest that loses provenance on round-trip.

Expected outcome: provenance review.

Prompt 6: Archive sync with KGSE

Coordinate with KGSE: the KG shifts to a new serializer
default in v1.6. What does LTAS do with:
- Existing archived KGs
- New archived KGs (from v1.6 onward)
- The transition window (format A + format B coexistence)

Produce a 6-row coordination table.

Expected outcome: coordination table.

  • Persona YAML: src/fcc/data/personas/long_term_archive_steward.yaml
  • Related prompts: persona-kgse-prompts.md, persona-dar-prompts.md, data-architects-polaris-archive.md
  • Planned: docs/tutorials/advanced-capabilities/polaris-archive-integration.md (Pool B)
  • Decoder: docs/ecosystem/codename-decoder.md (POLARIS entry)