Glossary and quick reference
| Term | Meaning in this application |
|---|---|
| Accountable owner | Person named as accountable for the described task or claim |
| Advisor review | Recorded human assessment of a record’s current completeness or meaning |
| Accepted source | Source reviewed for use; acceptance does not prove every assertion |
| Agent proposal | Draft assistance design bound to work versions, with no operative grant |
| Authority | Legitimate permission to act in a business context; separate from work description |
| Binding | Reference to an exact record version and hash used by another artifact |
| Case | One persisted instance of a reviewed manual workflow |
| Classification | Known, Inferred, Assumed or Missing label describing the stated basis |
| Company revision | Incrementing value identifying changes to the company’s record |
| Confirmation | A named participant’s decision about an exact task version/hash, later accepted by advisor |
| Constraint hypothesis | Testable explanation of what may limit overall output |
| Coverage | Explicit scope of roster, responses, tasks, observations or audit activity |
| Discriminator | Observation or test intended to distinguish competing explanations |
| Duty | Continuing responsibility that may contain several tasks |
| Evidence origin | Identity of the original source, used to avoid counting copies as independent |
| Export | Frozen internal record package; distinct from a reviewed client report |
| Framework | An evidence-bound analysis with defined upstream prerequisites |
| Guardrail | Condition that must remain acceptable while testing a change |
| Handoff | Contract describing what the receiving task requires and how exceptions are handled |
| Hash | Digest of canonical content or file bytes; not an approval signature |
| Human checkpoint | Described point where a person must review or decide |
| Idempotency | Retrying the same command key/content returns its prior result instead of repeating it |
| Intervention | Proposed change with owner, prediction, measure, stop conditions and review date |
| Locator | Reference precise enough to find the supporting passage or observation |
| Manual case observation | Advisor’s record of human work, not independent evidence of external execution |
| Outcome review | Interpretation against a preserved prediction and measurement snapshot |
| Performer | Person described as carrying out a task |
| Projection | Rebuildable graph metadata derived from authoritative records |
| Report audience | Explicit intended recipients whose names are frozen into a client packet |
| Roster | People in the bounded engagement; not necessarily the entire company |
| Source retraction | Removal of a source from current use while preserving history and marking dependencies stale |
| Stale | A record needs fresh review because its inputs, content or review period changed |
| Task | Bounded trigger-to-output work description |
| Tenant | Application isolation boundary for an account’s company data |
| Throughput | Completed system output per period, defined for the engagement |
| Workflow | Reviewed sequence and branches of tasks and receiving handoffs |
Before clicking Review
Check the current version, required fields, evidence, accountable people, unresolved conflicts, and scope. State why the review is justified. If the source changed, refresh the derived record before reviewing it.
Before saying Confirmed
Check that both required roles have accepted correct decisions for the current version and hash. Check the review date. Do not transfer a past confirmation to a new description.
Before saying Improved
Check the formula, cohort, source, baseline, observation window, target and confounders. Distinguish arithmetic movement from causal attribution. If the source is synthetic, say so.
Before saying Authorized or Deployed
The current local build does not establish either state for external business systems. A draft task, reviewed diagnosis, report approval or exported agent package does not change that. Consult the separate integration and production acceptance plan.
Before sending a client packet
Check audience, exact content, current bindings, exclusions, and limitations. Download the reviewed packet, inspect it and use the agreed channel. Keep a distribution record; the application does not send messages or recall downloaded copies.