The workflow entity and relationships.
Workflow graph
A workflow changes when any coordinate changes.
Planisphere maps the workflow before it tests anything: who uses it, where it runs, what data it touches, what output it produces, and which compliance gate it has to clear.
formal coordinates: D, Sigma, S, L, R, N, G_sign, G_text, Y, C_phil
01 ·
Every row pays a layer.
graph, normalization, harness, readout, source, clock
The translation into stable terms.
The test dependency this row must face.
The eventual PASS, PARTIAL, or FAIL surface.
The bytes, page, note, report, or run that anchors the row.
The time boundary. Freshness matters.
02 ·
Row contract.
No row, no harness. No harness, no evidence.
| Field | Why it exists | Example |
|---|---|---|
source_key | Prevents orphan workflow notes. | manual:dealflow |
payload_hash | Detects mutation. | sha-256 |
layer | Forces the row to pay rent. | harness |
normalization_note | Explains translation into stable language. | buyer context narrowed |
clock | Stops old truth from pretending to be current truth. | 2026-06-30 |
03 ·
Why graph first?
Because the harness needs something precise to hit
before graph unmapped workflow
Everyone argues about the demo.
after graph compliance coordinates
The workflow has source, layer, boundary, and clock.
after harness readout
The row survives, narrows, or fails.
after evidence report
Internal or external compliance sees what can and cannot be approved.