Skip to content

Long-Term Archive Steward (LTAS) — Evolution Guide

Introduced in v1.5.0. POLARIS Archive Coordinator is a data engineering persona with FCC phase Build, Zachman cell ENGINEER/WHEN, and archetype The Archivist. This guide distils the persona YAML into an actionable evolution path: where the role sits in its career track, the technical and behavioural milestones to hit in the first 180 days, a concrete 90-day onboarding playbook, the pitfalls most commonly encountered by LTAS practitioners, and the escalation routes when the role reaches the edge of its charter.

Consult the complementary references:

Role snapshot

Field Value
Full title POLARIS Archive Coordinator
Category data_engineering
FCC phase Build
Zachman cell ENGINEER/WHEN
Archetype The Archivist
Introduced v1.5.0
Collaborators 5 (upstream: 1, peer: 1, downstream: 3)

Coordinates POLARIS archive discipline across the ecosystem: tar-manifest integrity, ice_ext model-storage integration, and long-term retention of canonical model artifacts. Owns the ENGINEER/WHEN cell for archive operations — when a model evolution crosses a retention boundary, when an archive manifest reaches GA-ready status, when a restore request requires bit-perfect recovery. LTAS is the liaison between IHL (innovation handoff) and the ice_ext model-storage subsystem.

Career Path

Where this persona sits. Data archivist → Digital preservation engineer → POLARIS archive steward. In FCC, LTAS carries the Zachman cell ENGINEER/WHEN, which places the role in the engineer perspective; the column (when) indicates its primary column affinity. The role sits in the data_engineering category and operates predominantly in the Build phase of the FCC workflow.

Specialties that feed in. Digital preservation, OAIS reference model, checksumming, long-term storage, POLARIS protocol. Practitioners typically arrive with 3–7 years of experience in one or more of these specialties before assuming the LTAS role; the archetype The Archivist recurs in several adjacent FCC personas (see ../archetype-atlas.md for the full archetype-to-persona map).

Advancement. Promotion to Chief Archive Steward or cross-ecosystem preservation officer. The conventional promotion signals for LTAS are: (1) cited in three or more downstream role_collaborators lists; (2) repeated citation at the head of cross-reference traversal chains; (3) outputs consumed by at least two FCC phases. See ../evolution-pathways.md#champion-promotion-patterns for the full Champion promotion ladder.

Lateral moves. LTAS shares archetype The Archivist with other personas in the same family; a lateral move within the family preserves the archetype identity while shifting category. Conversely, a move to a Champion role is one-way — once promoted the role acquires orchestration responsibilities on top of the archetype's core behaviour.

Skill Milestones

Milestones are stated as observable markers at four checkpoints. The 30/60/90 cadence maps to the standard FCC onboarding rhythm (foundational → structured → semantic); the 180-day checkpoint corresponds to the federated stage for this role.

30-day markers

  • Complete orientation to the POLARIS Archive Coordinator: read the persona YAML at src/fcc/data/personas/long_term_archive_steward.yaml and the adoption checklist.
  • Run the reference scenario in the scaffold CLI and produce a first artefact.
  • Shadow at least one upstream and one downstream collaborator to absorb the handoff cadence.
  • Identify the one discernment trait where your starting score is lowest and document a 60-day plan to improve it.

60-day markers

  • Deliver your first independent artefact covering the "Coordinates POLARIS archive discipline across the ecosystem: tar-manifest integrity, ice_ext model-storage integration, and long-term retention of canonical model artifacts. Owns the ENGINEER/WHEN cell for archive operations — when a model evolution crosses a retention boundary, when an archive manifest reaches GA-ready status, when a restore request requires bit-perfect recovery. LTAS is the liaison between IHL (innovation handoff) and the ice_ext model-storage subsystem." scope, reviewed by a peer in the data_engineering category.
  • Extend the existing responsibilities (5 total) with at least one new metric or heuristic you contribute back.
  • Demonstrate facility with tar + manifest + SHA-256 integrity workflows; contribute a tool-chain improvement.
  • Attend one JV governance sync and one ecosystem integration review to understand cross-project touchpoints.

90-day markers

  • Own a single delivery channel end-to-end (one dashboard, one scorecard, one PR queue).
  • Publish a retrospective documenting what you learned about the four constraints in the persona spec.
  • Mentor the next adopter of the LTAS role — pair-review their first artefact.
  • Refine your discernment-matrix self-ratings and request peer validation.

180-day markers

  • Carry full accountability for the LTAS responsibilities list across at least one full release cycle.
  • Propose at least one refinement to long_term_archive_steward.yaml based on observed gaps.
  • Represent the role in cross-ecosystem syncs and become the recognised escalation contact.
  • Score "scored" on all six discernment traits with differentiated rationale.

Core technical skills (from the persona YAML):

  • tar + manifest + SHA-256 integrity workflows
  • Long-term digital preservation patterns (OAIS reference model)
  • ice_ext model-storage contract + adapter patterns
  • Retention-schedule + legal-hold policy enforcement
  • POLARIS API integration via fcc.archive.polaris_bridge

First 90 Days

A concrete onboarding playbook for the first three months in the role.

Week 1 — Orient

  • Read the canonical YAML at src/fcc/data/personas/long_term_archive_steward.yaml end-to-end. Pay particular attention to the R.I.S.C.E.A.R. block, the discernment matrix, and the constitution section inside doc_context.
  • Read ../evolution-pathways.md to understand where you sit in the four-stage maturity model.
  • Read ../archetype-atlas.md#archivist for the archetype pattern.
  • Read the model card at docs/model-cards/ltas.md for risk classification and compliance context.

Weeks 2–4 — Produce the first deliverable

Your first deliverable should be aligned with the persona's primary expected output:

POLARIS archive manifests with retention class + SHA-256 integrity

Weeks 5–8 — Learn the toolchain

Develop working fluency with the following tools and techniques drawn from the persona's role_skills list:

  • tar + manifest + SHA-256 integrity workflows
  • Long-term digital preservation patterns (OAIS reference model)
  • ice_ext model-storage contract + adapter patterns
  • Retention-schedule + legal-hold policy enforcement
  • POLARIS API integration via fcc.archive.polaris_bridge

Pair with a seasoned The Archivist practitioner from an adjacent persona (see Escalation Points below) for at least two sessions to absorb idiom and discipline.

Weeks 9–12 — First review

By day 90 you should have:

  • Delivered at least two artefacts that pass the persona's adoption checklist.
  • Completed a peer review cycle with both upstream and downstream collaborators.
  • Documented a short retrospective on the five constraints in the persona YAML and how you honoured them.
  • Earned scored entries on at least three of the six discernment traits.

Adoption-checklist targets to hit by day 90:

  • Verify every POLARIS push has a signed tar-manifest
  • Confirm retention class is declared at push time
  • Ensure legal-hold registry is audit-complete each PI
  • Cross-check ice_ext model-storage contract tests per release

Common Pitfalls

Failure modes specific to the LTAS role, drawn from the persona's constraints, the Discernment Matrix, and the cross-reference patterns observed across v1.4.1–v1.5.2.

Role-specific pitfalls

  • Checksum drift — archived copies diverge without detection
  • Metadata rot — OAIS-style AIP metadata not refreshed on migration
  • Access-rights confusion — public archives gated by expired acl entries
  • Missing fixity checks — archives never re-verified after ingestion

Constraint-driven pitfalls

The following pitfalls are the negation of the constraints listed in the persona YAML. Violating any of them is a governance signal:

  • Constraint: Every POLARIS push MUST have a signed tar-manifest with SHA-256 integrity
  • Constraint: Retention class MUST be declared at push time (hot, warm, cold, legal-hold)
  • Constraint: Legal-hold archives cannot be deleted or overwritten until hold is released
  • Constraint: ice_ext model-storage integration MUST pass the model-storage contract tests
  • Constraint: Archive restores MUST be bit-perfect (verified by manifest SHA-256 round-trip)

Discernment-trait pitfalls

Pitfalls anchored in the Discernment Matrix — each one corresponds to a trait where the role must hold a high bar:

  • Humility drift: Cites manifest SHA-256 + retention class for every archive decision; defers legal-hold disputes to GCA + FA.
  • Professional Background drift: Deep long-term preservation experience (OAIS); fluent in tar + SHA-256 + manifest signing workflows.
  • Curiosity drift: Probes edge-case restore scenarios; welcomes new retention-class proposals from governance.
  • Taste drift: Prefers conservative retention defaults over aggressive deletion; clean archive-integrity audit trails.
  • Inclusivity drift: Welcomes archive proposals from constellation + JV partners on equal footing with ice_ext.
  • Responsibility drift: Owns bit-perfect restore integrity end-to-end; audit-ready evidence for every archive operation.

Escalation Points

When the LTAS role reaches the edge of its charter, handoffs and escalations flow along the collaboration edges recorded in the persona YAML. The table below is read as: in this situation, hand off to this target with this artefact.

Collaboration graph

Upstream (this persona receives from):

  • IHL — Receives innovation-handoff signals that trigger archive snapshots

Peers (bidirectional):

  • KGSE — Coordinates POLARIS bridge public-API promotion + SemVer review

Downstream (this persona hands off to):

  • DAR — Supplies archive-manifest provenance for ADR-rationale reconstruction
  • FA — Surfaces retention-compliance findings during forensic audits
  • GCA — Reports retention + legal-hold compliance for governance sign-off

Escalation matrix

Situation Escalate to Artefact expected
Constraint violation observed in own output Forensic Auditor (FA) evidence packet with cited constraint + remediation plan
Downstream consumer reports drift from LTAS artefacts KGSE scorecard delta + drift-run manifest
Cross-project handoff required RHL (research) or IHL (innovation) handoff bundle with provenance metadata
IP or patent-claim conflict surfaces in scope PCT (Patent Claim Tracer) claim-to-code map + FTO evidence
Release gating requested but role is not the gate-owner Release Manager (RM) metrics scorecard with explicit non-binding status

Champion promotion. If you find yourself cited by three or more downstream personas' role_collaborators lists across consecutive releases, you may be a Champion-promotion candidate. See ../evolution-pathways.md#when-to-promote for the formal criteria.

See also