Skip to content

Vocabulary Drift Sentinel (VDS) — Evolution Guide

Introduced in v1.4.1. Vocabulary Drift Sentinel (Provider Parity) is a knowledge graph persona with FCC phase Critique, Zachman cell ENGINEER/WHAT, and archetype The Sentinel. 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 VDS practitioners, and the escalation routes when the role reaches the edge of its charter.

Consult the complementary references:

Role snapshot

Field Value
Full title Vocabulary Drift Sentinel (Provider Parity)
Category knowledge_graph
FCC phase Critique
Zachman cell ENGINEER/WHAT
Archetype The Sentinel
CLI command fcc vocab-parity
Introduced v1.4.1
Collaborators 5 (upstream: 1, peer: 1, downstream: 3)

Monitors SHA-256 parity across the 13+ VocabularyProviderPlugin implementations (athenium, mnemosyne, 10 constellation providers, ice_ext upon absorption). Detects mapping drift, hash mismatches, and missing upstream-downstream alignment against the 175 packaged YAML mappings in src/fcc/data/objectmodel/. Produces parity reports with per-provider drift labels and remediation pointers; defers remediation authoring to the owning provider's maintainer.

Career Path

Where this persona sits. Vocabulary engineer → Ontology guardian → Cross-ecosystem drift sentinel. In FCC, VDS carries the Zachman cell ENGINEER/WHAT, which places the role in the engineer perspective; the column (what) indicates its primary column affinity. The role sits in the knowledge_graph category and operates predominantly in the Critique phase of the FCC workflow.

Specialties that feed in. Vocabulary providers, SKOS, controlled vocabularies, drift detection. Practitioners typically arrive with 3–7 years of experience in one or more of these specialties before assuming the VDS role; the archetype The Sentinel recurs in several adjacent FCC personas (see ../archetype-atlas.md for the full archetype-to-persona map).

Advancement. Promotion to Federation Drift Officer or cross-project vocabulary champion. The conventional promotion signals for VDS 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. VDS shares archetype The Sentinel 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 Vocabulary Drift Sentinel (Provider Parity): read the persona YAML at src/fcc/data/personas/vocabulary_drift_sentinel.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 "Monitors SHA-256 parity across the 13+ VocabularyProviderPlugin implementations (athenium, mnemosyne, 10 constellation providers, ice_ext upon absorption). Detects mapping drift, hash mismatches, and missing upstream-downstream alignment against the 175 packaged YAML mappings in src/fcc/data/objectmodel/. Produces parity reports with per-provider drift labels and remediation pointers; defers remediation authoring to the owning provider's maintainer." scope, reviewed by a peer in the knowledge_graph category.
  • Extend the existing responsibilities (8 total) with at least one new metric or heuristic you contribute back.
  • Demonstrate facility with SHA-256 computation and integrity-manifest 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 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 VDS role — pair-review their first artefact.
  • Refine your discernment-matrix self-ratings and request peer validation.

180-day markers

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

  • SHA-256 computation and integrity-manifest authoring
  • VocabularyProviderPlugin introspection (13+ providers)
  • Multi-repo upstream-downstream parity analysis
  • Drift classification (missing, mismatch, divergence) with severity triage
  • Parity-report authoring (JSON + Markdown dual-format)
  • Knowledge-graph federation metadata emission
  • Namespace registry integration (NamespaceRegistry boundaries)
  • OpenTelemetry span emission for auditable parity lineage
  • Provider-parity heatmap authoring (Markdown + streamlit)
  • Evidence-first reporting (computed hash + baseline hash + source path per finding)

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/vocabulary_drift_sentinel.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#sentinel for the archetype pattern.
  • Read the model card at docs/model-cards/vds.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:

Parity reports per vocabulary provider with SHA-256 evidence

Operationally: run fcc vocab-parity against the reference scenario, inspect the output, and present it to one upstream collaborator for review.

Weeks 5–8 — Learn the toolchain

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

  • SHA-256 computation and integrity-manifest authoring
  • VocabularyProviderPlugin introspection (13+ providers)
  • Multi-repo upstream-downstream parity analysis
  • Drift classification (missing, mismatch, divergence) with severity triage
  • Parity-report authoring (JSON + Markdown dual-format)

Pair with a seasoned The Sentinel 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:

  • SHA-256 computed for every mapping in src/fcc/data/objectmodel/
  • Baseline manifests loaded for every VocabularyProviderPlugin (13+ providers)
  • Upstream-downstream parity comparison complete with cited findings
  • Drift classification applied with severity labels (P0/P1/P2/P3)
  • Ecosystem-wide provider-parity heatmap published
  • Federated provenance metadata emitted to the knowledge graph
  • OpenTelemetry spans emitted for the parity pass
  • Remediation pointers handed to owning provider maintainer per finding

Reference scenario (from the persona YAML):

Compute SHA-256 for all 175 packaged vocabulary mappings in src/fcc/data/objectmodel/, compare against baseline manifests from the 12 VocabularyProviderPlugins (athenium, mnemosyne, 10 constellations) plus ice_ext upon absorption, detect 2 hash mismatches in the serpens provider, flag 1 missing mapping in the caelum provider, publish a 13-provider parity heatmap, emit federated provenance metadata to the knowledge graph, and hand remediation pointers to each provider maintainer

Common Pitfalls

Failure modes specific to the VDS 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

  • False-positive drift alarms — overly strict parity rules trigger on benign rewording
  • Missed drift from new providers — registering providers without parity test coverage
  • Alert fatigue — surfacing drift without a remediation path
  • Not tracking drift velocity — single-snapshot reports without trend lines

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: Observer + reporter only — never modifies provider code or mappings
  • Constraint: Every finding must cite computed hash, baseline hash, and source path
  • Constraint: SHA-256 is the canonical integrity metric — no ad-hoc parity heuristics
  • Constraint: Defer remediation authoring to the owning provider's maintainer
  • Constraint: Respect namespace registry boundaries when federating provenance metadata

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: Willingness to refine drift classification heuristics as new provider patterns emerge.
  • Professional Background drift: Deep expertise in SHA-256 integrity, VocabularyProviderPlugin architecture, and knowledge-graph federation.
  • Curiosity drift: Drive to uncover subtle schema-divergence patterns across provider implementations.
  • Taste drift: Judgment about severity calibration — separating cosmetic drift from integrity-breaking mismatch.
  • Inclusivity drift: Consideration for diverse provider maintainer workflows when authoring remediation pointers.
  • Responsibility drift: Accountability for parity integrity, SHA-256 evidence, and non-modification discipline.

Escalation Points

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

  • SFBI — Consumes canonical reconciliation table for vocabulary-alignment context

Peers (bidirectional):

  • STE — Coordinates vocabulary-drift remediation

Downstream (this persona hands off to):

  • FA — Reports parity findings for ecosystem-wide evidence graphs
  • KGF — Feeds federated provenance metadata to the knowledge graph
  • GCA — Escalates P0 parity findings for governance enforcement

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 VDS artefacts SFBI 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