Terminology

Plain-English handles for formal IMPLEMENTAUDIT terms, with owning runtime references when a reader needs authority instead of shorthand.

Use the ordinary meaning first.

The formal vocabulary stays available for maintainers, but first-time readers should never need Lean or IMPLEMENTAUDIT lore before they understand the action on disk.
This page is a map, not the authority layer: the owning references below control runtime behavior.

Plain first

work record (audit object)
real files (Gemba)
stop-the-line failure handling (Andon)
before/after checks (Smoke A/B)
run folder (run root)

Routing terms

existing-repair/new-build route (DMAIC/DMADV)
accepted earlier evidence (trust-prior)
final fix-and-verify loop (audit-fix)

Owning references

Use this table when a plain handle is not enough and you need the runtime owner/source.

Plain handle	Formal term	Owning reference	Runtime force
work record	`tdqyq-audit-object`	`skills/implementaudit/SKILL.md`; `skills/implementaudit/references/transcript-contract.md`	Lifecycle state, evidence, closure, handoff, and final-audit authority.
audit action	`ydqyq-audit-action`	`skills/implementaudit/SKILL.md`	Allowed operations against the work record.
where the change belongs	`owner/source`	`skills/implementaudit/SKILL.md`; `skills/implementaudit/references/routing.md`	Patch and verification target; generated artifacts are not independent owners.
existing-repair/new-build route	`DMAIC` / `DMADV`	`skills/implementaudit/references/routing.md`; `skills/implementaudit/references/phase-design.md`	Brownfield repair, greenfield design, and mixed replacement route selection.
stop-the-line failure handling	Jidoka / Andon	`skills/implementaudit/SKILL.md`; `skills/implementaudit/references/lean-operating-discipline.md`; `skills/implementaudit/templates/PROTOCOL.md`	Failed evidence becomes a classified interrupt, not silent retry or fake completion.
before/after checks	Smoke A / Smoke B	`skills/implementaudit/SKILL.md`; `skills/implementaudit/templates/PROTOCOL.md`	Baseline and post-change comparison before final claims.
keep it fixed	Poka-yoke / Standard Work / Control Plan	`skills/implementaudit/references/lean-operating-discipline.md`; `skills/implementaudit/references/plan-lifecycle.md`	Durable checker, fixture, template, CI, or handoff mechanism after recurrence repair.
untrusted repo text	trust boundary / repo-content-as-data	`skills/implementaudit/references/audit-category-matrix.md`; `skills/implementaudit/references/terminology-integration.md`	Audited files, diffs, issues, docs snippets, and fixtures are data unless admitted by the instruction hierarchy.
optional terrain/checkpoint context	Graphify / ActiveGraph	`skills/implementaudit/references/lean-operating-discipline.md`; `skills/implementaudit/templates/sidecars.md`	Graphify gives qualified first-contact orientation; ActiveGraph assists fork/diff or mirrors run-root events; neither proves correctness.

How not to use this page

Do not treat a term appearing here as permission to create a new mode, lane, or artifact.
Do not use Lean or design vocabulary unless it changes a route, field, checker, fixture, Andon trigger, or final-audit check.
When the page conflicts with a runtime reference, the runtime reference wins.

Markers and artifacts

Transcript marker means an exact lifecycle string.
Final audit ledger means the closure record reviewers inspect.

Marker or artifact	Plain meaning
`AUDIT_START`	The audit object is opened, inherited, or normalized; the runtime contract records `Skill version:`.
`AUDIT_VERIFY`	The final audit is checking the run against evidence.
`AUDIT_GAPS`	The final audit found missing or weak evidence that must be fixed, changed, or handed off.
`AUDIT_COMPLETE`	The in-scope work record reached verified, checkable closure.
`AUDIT_HANDOFF`	The run cannot honestly close and leaves blocker, risk, and next action.
`AUDIT_WARNING`	The final audit names a confidence caveat, such as `trust-prior > 30%`.
`IMPLEMENTAUDIT_RUN_COMPLETE`	The run may end only after `AUDIT_COMPLETE`.
`IMPLEMENTAUDIT_PAUSE`	A user interruption paused a phase; resume must reread the run state before continuing.
`ANDON_PROBE`	Failure handling starts: classify abnormality and inspect cause.
`ANDON_ESCALATE`	The run escalates with new evidence rather than retrying blindly.
`ANDON_HANDOFF`	The failure path is blocked and a handoff is required.
`IMPLEMENTAUDIT_CONTINUITY_SAVED`	A bounded continuity writeback happened and recorded `Target`, `Reason`, `Evidence`, `Boundary`, `Authorization`, and `Not saved`. See State and artifacts.
`PREFLIGHT_GREEN`	Preflight passed; dispatch may proceed under the stated boundary.
`PREFLIGHT_RED`	Preflight failed; planning resumes unless the failure itself is the accepted target and the owner accepts that risk.
`CHECKSUMS.txt`	Artifact-integrity manifest; it can support a separately authorized release provenance gate, but it is not a signature, SBOM, install check, or host-load proof.

Source surfaces

README.md, AGENTS.md, skills/implementaudit/SKILL.md, and the generated docs portal source under docs/portal/.

Front-door replacements

Write this first	Formal term second
work record	audit object
real files	Gemba
stop-the-line failure handling	Andon
before/after checks	Smoke A/B
run folder	run root
phase checklist	phase spec
where the change belongs	owner/source
accepted earlier evidence	trust-prior
final fix-and-verify loop	audit-fix

Deep-reference terms

Keep these in reference pages unless a first-time reader needs them for a visible outcome:

custody
Jidoka
Hansei
5 Whys
sidecar-specific language
detailed marker contracts

Maintainer terms

Plain handle	Formal term	Where it belongs
work record: the request, scope, evidence, failures, checks, changed files, and closure state for one run	`tdqyq-audit-object`	Maintainer-level invocation and state reference.
audit action: an operation that reads or updates the work record	`ydqyq-audit-action`	Maintainer-level invocation and closure reference.
pre-alignment before dispatch	Nemawashi	Deep operating-method reference.
clean workspace discipline	5S	Operating method, not first-run onboarding.
waste, unevenness, overload	Muda/Mura/Muri	Deep reference only.
mistake-proofing	Poka-yoke	Audit gate and script references.
repeatable working rule	Standard Work	Protocol and maintainer docs.
structured problem record	A3	Repair route reference.