Skip to content

Real-Corpus Refresh Steward (RCRS) — Evolution Guide

Introduced in v1.7.0. Real-Corpus Refresh Steward is a data-engineering persona with FCC phase Find, Zachman cell PLANNER/WHAT, and archetype The Steward. 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 RCRS practitioners, and the escalation routes when the role reaches the edge of its charter.

Consult the complementary references:

Role snapshot

Field Value
Full title Real-Corpus Refresh Steward
Category data_engineering
FCC phase Find
Zachman cell PLANNER/WHAT
Archetype The Steward
Introduced v1.7.0
Collaborators 6 (upstream: 2, peer: 2, downstream: 2)

Operates the quarterly real-corpus refresh cycle for FCC's six seed-data pillars (personas, ecosystems, mappings, scenarios, diagrams, and publications). Coordinates with pillar-a-steward on long-term provenance, validates upstream licenses, generates manifest SHA256s, and ensures every refresh is reproducible, auditable, and license-clean.

Career Path

Where this persona sits. Data engineer → Corpus curation specialist → Data-refresh steward and license compliance coordinator. In FCC, RCRS carries the Zachman cell PLANNER/WHAT, which places the role in the planner perspective; the column (what) indicates its primary affinity with data, artefacts, and the inventories of what exists. The role sits in the data_engineering category and operates predominantly in the Find phase of the FCC workflow.

Specialties that feed in. Data provenance tracking, SHA256/BLAKE2b manifest discipline, SPDX license analysis, FAIR data principles, Airflow/Prefect pipeline authoring, and patience with long-running refresh cycles. Practitioners typically arrive with 3–7 years of experience in one or more of these specialties before assuming the RCRS role; the archetype The Steward recurs in several adjacent FCC personas (see ../archetype-atlas.md for the full archetype-to-persona map).

Advancement. Promotion to Corpus Governance Champion (orchestrates RCRS, pillar-a-steward, LTAS, seed-canonical-reviewer) or cross-ecosystem data-steward. The conventional promotion signals for RCRS 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. RCRS shares archetype The Steward with LTAS and pillar-a-steward; a lateral move preserves the archetype identity while shifting focus between long-term archival, refresh operations, and long-term pillar ownership. 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 Real-Corpus Refresh Steward role: read the persona YAML at src/fcc/data/personas/real_corpus_refresh_steward.yaml and the adoption checklist.
  • Run the v1.7.0 refresh dry-run against a single pillar and produce a first manifest diff report.
  • Shadow at least one LTAS archive cycle and one seed-canonical-reviewer review cycle.
  • 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: a refresh runbook covering the end-to-end process for one pillar with manifest + license checks.
  • Extend the existing responsibilities (6 total) with at least one new metric or heuristic you contribute back.
  • Demonstrate facility with SHA256/BLAKE2b manifest discipline, SPDX license scanning, and Airflow/Prefect workflow authoring; 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 pillar's refresh cycle end-to-end (source discovery, license check, manifest generation, seed upload, documentation update).
  • Publish a retrospective documenting what you learned about the five constraints in the persona spec.
  • Mentor the next adopter of the RCRS role — pair-review their first artefact.
  • Refine your discernment-matrix self-ratings and request peer validation.

180-day markers

  • Carry full accountability for the RCRS responsibilities list across at least one full release cycle.
  • Propose at least one refinement to real_corpus_refresh_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):

  • Manifest discipline (SHA256 / BLAKE2b pinning, provenance chain)
  • SPDX license scanning + compatibility reasoning
  • FAIR data principles (Findable, Accessible, Interoperable, Reusable)
  • Airflow / Prefect / DAG authoring for refresh pipelines
  • Reproducible download + caching discipline (lockfiles, mirrors)

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/real_corpus_refresh_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#steward for the archetype pattern.
  • Read the model card at docs/model-cards/rcrs.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: a per-pillar refresh report with manifest delta, license audit, and reproducibility-run transcript.

Weeks 5–8 — Learn the toolchain

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

  • Manifest discipline (SHA256 / BLAKE2b pinning, provenance chain)
  • SPDX license scanning + compatibility reasoning
  • FAIR data principles (Findable, Accessible, Interoperable, Reusable)
  • Airflow / Prefect / DAG authoring for refresh pipelines
  • Reproducible download + caching discipline (lockfiles, mirrors)

Pair with a seasoned Steward practitioner (LTAS or pillar-a-steward) 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:

  • Every refresh cycle has a signed manifest with SHA256 pinning.
  • Every corpus entry passes SPDX license-compatibility check.
  • Refresh runbooks are reproducible from a clean clone (no undocumented prerequisites).
  • Downstream seed consumers (POLARIS, LYRA, constellation vocab) pin to explicit RCRS refresh IDs.

Common Pitfalls

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

Role-specific pitfalls

  • Downloading refresh sources on the critical path without mirror + cache, leading to flaky CI.
  • Letting a corpus entry slip through with an incompatible license (GPL mixed into MIT without opt-in documentation).
  • Producing a manifest without BLAKE2b, relying on SHA256 alone after a cryptographic downgrade scare.
  • Refreshing a pillar without notifying pillar-a-steward, leading to long-term provenance gaps.

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 refresh cycle MUST produce a signed manifest with SHA256 + BLAKE2b pinning.
  • Constraint: Every corpus entry MUST pass SPDX license-compatibility check against the MIT core.
  • Constraint: No refresh MAY land without seed-canonical-reviewer signoff.
  • Constraint: Refresh cycles MUST be reproducible from a clean clone with only public registries.
  • Constraint: Long-term provenance chain MUST be updated with pillar-a-steward co-signature.

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: Escalates ambiguous licensing to legal counsel (PCT); never makes unilateral compatibility calls.
  • Professional Background drift: Deep data-engineering + provenance experience; fluent in FAIR data principles.
  • Curiosity drift: Probes every upstream source for license changes, repository migrations, and dependency drift.
  • Taste drift: Prefers small, focused refreshes over mega-batch rewrites; clean manifest discipline.
  • Inclusivity drift: Welcomes community corpus contributions with clear licensing guidance.
  • Responsibility drift: Owns refresh-cycle integrity; audit-ready manifest chain across all six pillars.

Escalation Points

When the RCRS 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):

  • LPA — Receives findings on portability issues in refreshed corpus.
  • IHR — Receives flags for corpus entries needing translation updates.

Peers (bidirectional):

  • LTAS — Coordinates long-term archive snapshots with refresh cycles.
  • pillar-a-steward — Aligns refresh cadence with long-term pillar ownership.

Downstream (this persona hands off to):

  • seed-canonical-reviewer — Hands refresh manifest + license notices for committee review.
  • PCT — Escalates IP / patent-claim conflicts surfaced in refreshed corpus.

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 RCRS artefacts LTAS scorecard delta + drift-run manifest
Cross-project handoff required RHL (research) or IHL (innovation) handoff bundle with provenance metadata
License compatibility question surfaces PCT (Patent Claim Tracer) SPDX report + legal-review request
Refresh requires owner approval for download Release Manager (RM) refresh scope + source list + license summary

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

See also