Purpose
This page renders the uploaded human workflow against the implemented workflow as a single colleague-review diagram.
It is intentionally more detailed than the earlier draw.io comparison. The implemented lane shows the actual database tables used, where the workflow matches the human reference, where it expanded beyond the reference, and where the design is still partial or missing as a strict workflow capability.
The human intake approach is shown explicitly as a first-class input: the uploaded workflow image was logged in documentation and as an immutable audit event before the comparison was built.
Detailed Workflow Diagram
How To Read It
| Marker | Meaning |
|---|---|
| Matched | The implemented workflow corresponds directly to the uploaded human workflow step. |
| Partial | The intent exists, but not as one strict universal workflow/state model. |
| Added | The implemented build goes beyond the uploaded workflow. |
| Missing | The uploaded workflow implies a distinct lane or object model that is still not explicit in the implementation. |
The right lane references the live build in database terms. The diagram uses actual table names because the point is to defend what the system does, not just describe it loosely.
Source Files
| Artifact | Path |
|---|---|
| Draw.io source | docs/architecture/EARTHBOND_REFERENCE_VS_IMPLEMENTED_WORKFLOW.drawio |
| Detailed SVG source | docs/architecture/EARTHBOND_REFERENCE_VS_IMPLEMENTED_WORKFLOW_DETAILED.svg |
| Human input log | docs/operations/HUMAN_INPUT_WORKFLOW_LOG_20260331.md |
| Alignment report | docs/architecture/REFERENCE_WORKFLOW_ALIGNMENT_REPORT_MANUAL.html |
| Generator | scripts/dev/generate_reference_workflow_diagram.py |