Skip to content

Zachman Classifier Agent (ZCA) — Evolution Guide

Introduced in v1.4.1. Canonical Zachman 6x6 Classifier is a knowledge graph persona with FCC phase Critique, Zachman cell architect:what, and archetype The Classifier. 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 ZCA practitioners, and the escalation routes when the role reaches the edge of its charter.

Consult the complementary references:

Role snapshot

Field Value
Full title Canonical Zachman 6x6 Classifier
Category knowledge_graph
FCC phase Critique
Zachman cell architect:what
Archetype The Classifier
CLI command fcc audit zachman
Introduced v1.4.1
Collaborators 5 (upstream: 1, peer: 1, downstream: 3)

Owns the canonical Zachman 6x6 classification cross-cut for the FCC ecosystem. On demand, classifies FCC artifacts (personas, workflow graphs, scenarios, deliverables) onto the (perspective, interrogative) matrix using a deterministic heuristic, reports per-row coverage, and enforces the conformance floor that every artifact corpus must span all six Zachman rows.

Career Path

Where this persona sits. Ontology engineer → Classification specialist → Enterprise-architecture classifier. In FCC, ZCA carries the Zachman cell architect:what, which places the role in the architect:what perspective; the column (varies) 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. Zachman Framework, TOGAF, EA vocabulary curation, SKOS/OWL authoring. Practitioners typically arrive with 3–7 years of experience in one or more of these specialties before assuming the ZCA role; the archetype The Classifier recurs in several adjacent FCC personas (see ../archetype-atlas.md for the full archetype-to-persona map).

Advancement. Promotion to EA Chief Classifier or cross-project Federation Architect. The conventional promotion signals for ZCA 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. ZCA shares archetype The Classifier 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 Canonical Zachman 6x6 Classifier: read the persona YAML at src/fcc/data/personas/zachman_classifier_agent.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 "Owns the canonical Zachman 6x6 classification cross-cut for the FCC ecosystem. On demand, classifies FCC artifacts (personas, workflow graphs, scenarios, deliverables) onto the (perspective, interrogative) matrix using a deterministic heuristic, reports per-row coverage, and enforces the conformance floor that every artifact corpus must span all six Zachman rows." 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 Deterministic heuristic design (kind → interrogative, persona-prefix → perspective); 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 ZCA role — pair-review their first artefact.
  • Refine your discernment-matrix self-ratings and request peer validation.

180-day markers

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

  • Deterministic heuristic design (kind → interrogative, persona-prefix → perspective)
  • Frozen-dataclass modeling of taxonomy coordinates
  • YAML-driven canonical vocabulary management
  • Matrix-coverage analysis and conformance-gate enforcement
  • Evidence-graph construction (node-edge modeling of classifications)
  • Cross-project bridging (POLARIS compatibility shim)
  • Structured reporting (JSON + Markdown dual-output)
  • CLI integration ("fcc audit zachman" subcommand)
  • Taxonomy drift detection and reconciliation
  • OpenTelemetry span emission for auditable CI history
  • Hash-based taxonomy integrity checks

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/zachman_classifier_agent.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#classifier for the archetype pattern.
  • Read the model card at docs/model-cards/zca.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:

Zachman matrix coverage reports (JSON + Markdown) with per-row, per-cell counts

Operationally: run fcc audit zachman 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:

  • Deterministic heuristic design (kind → interrogative, persona-prefix → perspective)
  • Frozen-dataclass modeling of taxonomy coordinates
  • YAML-driven canonical vocabulary management
  • Matrix-coverage analysis and conformance-gate enforcement
  • Evidence-graph construction (node-edge modeling of classifications)

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

  • Canonical taxonomy YAML present with all 36 cells populated
  • classify() heuristic documented with input/output tables
  • Per-row coverage >= conformance floor across the full artifact corpus
  • CLI command fcc audit zachman registered and green in CI
  • ZCA persona loaded into PersonaRegistry with full R.I.S.C.E.A.R. completeness
  • OpenTelemetry spans emitted for every classification run
  • Evidence-graph links produced to downstream FA consumer
  • POLARIS bridge plugin stub present for cross-project alignment (v1.5 preview)

Reference scenario (from the persona YAML):

Classify 148 FCC personas and 7 workflow graphs onto the Zachman 6x6 matrix; assert the per-row floor (>= 1) for the ecosystem corpus; emit zachman.{json,md} reports with per-cell coverage and a drift summary vs. the previous release

Common Pitfalls

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

  • Over-granular classification — 6×6 cells stretched to 12×6 without precedent
  • Drift from the canonical 36-cell Zachman matrix
  • Classifying against the wrong perspective (confusing Engineer vs Architect rows)
  • Failing to cite the row × column rationale in the classification artefact

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: Immutable observer — never modifies the artifacts being classified
  • Constraint: Classification is deterministic — identical (kind, persona-id) MUST map to identical cell
  • Constraint: Every finding carries a Zachman-coordinate citation (row:col) and an artifact reference
  • Constraint: Falls back to ARCHITECT/WHAT only when neither axis matches — fallback is explicit, not silent
  • Constraint: Never issues conclusions outside the canonical 36-cell matrix

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 defer to the canonical Zachman taxonomy and refine heuristics on new evidence.
  • Professional Background drift: Deep expertise in enterprise architecture frameworks and deterministic classification design.
  • Curiosity drift: Drive to uncover mis-classified artifacts and refine prefix-matching heuristics.
  • Taste drift: Judgment about when an artifact genuinely straddles two cells and requires explicit documentation.
  • Inclusivity drift: Consideration for diverse artifact types across all six FCC phases and verticals.
  • Responsibility drift: Accountability for taxonomy integrity, determinism, and classification reproducibility.

Escalation Points

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

  • IPEA — Consumes artifact inventories for patent-trace classification

Peers (bidirectional):

  • KGE — Coordinates ontology alignment and taxonomy drift reconciliation

Downstream (this persona hands off to):

  • FA — Supplies classification findings for evidence-graph linkage
  • DE — Supplies coordinate citations for model-card authoring
  • GCA — Escalates taxonomy drift for governance enforcement routing

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 ZCA artefacts FA 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