Developers: Adding zachman_cell to New Artifacts (v1.4.1+)¶
Since v1.4.1 every FCC artifact MAY carry a zachman_cell
attribute. The fcc audit zachman CLI checks per-row floor
coverage and surfaces unclassified artifacts. These five prompts
walk a developer through tagging a new artifact correctly on the
first commit.
Personas Used¶
| Persona ID | Full Name | Role |
|---|---|---|
| dal | Data Analyst Lead | Picks the cell |
| tr | Technical Reviewer | Reviews the tagging |
| ZCA | Zachman Cross-Cut Analyst | Validates coverage |
Prompt 1: Pick the Right Cell¶
Personas: dal, ZCA
Prompt¶
dal, I am adding a new workflow graph called `triage_stream` that
handles incoming customer tickets. Walk me through deciding its
zachman_cell. Consider: what the workflow produces, who it serves,
and where in the 6x6 matrix this lands most naturally.
Deliverable: the chosen coordinate string (e.g., "architect/how"),
a 2-sentence rationale, and a runner-up cell in case review
pushes back.
Expected Output¶
- Chosen coordinate
- Two-sentence rationale
- Runner-up coordinate
Prompt 2: Serialize the Cell¶
Personas: tr
Prompt¶
tr, show the YAML front-matter snippet that attaches
zachman_cell: "architect/how" to the new workflow graph file.
Include the description field drawn from the canonical taxonomy
(zachman_taxonomy.yaml). Round-trip the cell through
ZachmanCell.to_dict() + from_dict() in a unit test.
Expected Output¶
- Front-matter snippet
- Round-trip test
- Taxonomy lookup step
Prompt 3: Run the Audit¶
Personas: ZCA
Prompt¶
Run `fcc audit zachman` and capture the output. If the new
workflow does not yet appear in the per-row coverage, list the
file globs the auditor scans and propose a patch to include the
workflow directory.
Expected Output¶
- Captured CLI output
- Glob inventory
- Patch proposal
Prompt 4: Defend the Choice¶
Personas: dal, ZCA
Prompt¶
A reviewer argues your workflow belongs in ENGINEER/WHAT, not
ARCHITECT/HOW. Produce a 100-word defense that cites the
canonical cell description from zachman_taxonomy.yaml. Be willing
to change your mind if the review has merit.
Expected Output¶
- 100-word defense OR retraction
- Taxonomy citation
- Honest stance
Prompt 5: Teach the Recipe¶
Personas: dal
Prompt¶
Distill the above into a 5-bullet checklist the team can pin to
the contributing guide. Include the command to re-run the audit
before each commit.
Expected Output¶
- 5-bullet checklist
- Pre-commit command
- Link to taxonomy source