Workflow Discovery Pack

Use for one customer or internal workflow. Capture only what is needed for the next decision; expand the packet as evidence and commitments mature.

Inherited story and accountable field roles

Preserve the brief as received before improving or reconciling it. Treat it as an evidence-bearing hypothesis, not current truth.

Do not infer the process knower, operator, disposition authority, or verifier from the sponsor. One person may hold multiple roles only when each role has a separate, recorded basis.

Engagement charter

Use the machine-readable workflow-charter template for the governed decision after discovery.

Strategic and operating apertures

Use this as a reconciliation pass, not a fixed interview script. Begin with the widest relevant view that is available, inspect the work and its technical seams, then return unresolved differences to the people who hold the relevant decision rights.

Do not require a customer-visible effect when an internal safety, control, or operating decision is more consequential. Do not treat executive sponsorship, interview volume, a survey, or a roadmap as proof of the workflow or permission to proceed.

Field evidence register

Field claim comparison and accountable reframe

No claim class universally outranks another or grants authority. Observation proves occurrence in scope; system testing proves exact-build behavior; policy remains normative within its revision and scope; a stakeholder assertion proves only that it was stated.

When field evidence materially changes the brief, use the machine-readable engagement-reframe record to preserve the competing claims, scoped decision, selective downstream impact, and chronology.

Interaction receipts and current readout

Keep source material separate from proposed conclusions. For each meeting, observation, incident review, or artifact handoff, record the interaction ID, engagement boundary, source revisions, proposed additions, named review disposition, appended record IDs, and timestamp in the field-observation log. Preview the changes before append; rejected and deferred proposals remain visible.

The sponsor readout is a projection of these dated receipts and the current governed records. It states the evidence cutoff, current boundary, measured outcome, unresolved consequential decision, next move, and source links. Do not maintain it as an independent status artifact or let it silently override the engagement reframe, value case, release evidence, or service review.

Workflow event log

Source-of-truth map

Technical reality check

Use direct evidence to test the stated workflow before assigning readiness or proposing architecture. A questionnaire, interview, diagram, or maturity score organizes hypotheses; it does not prove the target environment is ready.

Mark an uninspected decision-bearing surface unknown. Do not infer readiness from document completeness or replace missing target access with a higher confidence score.

Decision decomposition

Context extraction and operational redesign

Interview notes, recordings, documents, and demonstrations are discovery evidence. They do not become prompts, policy, memory, or production authority until the owning role validates them.

| Candidate knowledge | Observed source and owner | Classification / scope | Type | Validate with | Keep, repair, remove, escalate, or abstract | Production destination / invalidation trigger | | --- | --- | --- | --- | --- | --- | | | | Public / internal / confidential / restricted | Fact / rule / judgment / workaround / exception / instruction | | | |

Use this table to distinguish current evidence from rules, professional judgment, and historical scar tissue. Keep customer-specific context with the workflow owner. A reusable product or pattern candidate must be sanitized, recurrence-tested, and routed through the field-learning register; never copy customer data or local policy into a shared artifact.

Exception taxonomy

Operational ontology candidates

Value-verifiability matrix

gross_annual_value = annual_volume × (
  minutes_per_case / 60 × loaded_labor_cost_per_hour
  + error_rate × error_cost_per_event
)

risk_adjusted_verified_value =
  gross_annual_value
  × verifier_coverage
  × adoption_probability
  × (1 - residual_risk_probability)

priority_ratio = risk_adjusted_verified_value
                 / max(1 currency unit, annualized_integration_and_operating_cost)

Use one declared currency and annual period. Bound every probability or coverage input to 0..1, preserve low/expected/high scenarios, and do not compare ratios built from different units or periods. This ratio ranks qualified candidates; it does not override a hard owner, verifier, authority, safety, or adoption gate. Keep estimated, measured, and realized value separate. Complete the value-case template before a pilot decision.

Assumption and decision log

Readiness gates

Copy these seven dimensions and their evidence into workflow-charter.readiness. Authenticated authority, accountable ownership, and a lawful data path remain independent hard gates even when the scored dimensions are otherwise strong.

Adoption and ownership plan

Stakeholder value and change contract

Controls: FDE-001, FDE-002, FDE-003, FDE-004, FDE-005, ADP-001, CTX-001, CTX-002.

Cutover plan