Status Vocabulary

Status: Binding claim vocabulary for this wiki

Authority: Current contract validation gates and wiki surface plan

Last reviewed: 2026-08-14

Question

What do implemented, verified, validated, and accepted mean here?

Short answer

These four words are different claims. Do not treat them as synonyms.

Term	Meaning
Implemented	Code or UI exists and can run the described behavior
Verified	Software tests or deterministic checks confirm the behavior
Validated	Representative human-reviewed truth supports an accuracy or usefulness claim
Accepted	An owner decision binds the product or architecture boundary

Extra labels used in this wiki

Term	Meaning
Current contract	Written rule for current algorithm roles and stage ownership
Evaluation evidence	Measured local result; not yet a validated accuracy claim
Plan draft	Intended work; not implemented unless another source confirms it
Work-in-progress	Present in an active implementation worktree; not merged accepted state
Strategy freeze	Temporary stop that preserves retained work while the next route is chosen
Historical tracking	Older status useful for history only

Common misreads

A model score is not validated truth. A local timing result is evaluation evidence, not a product SLA. A software test verifies behavior. A software test does not validate drawing accuracy. A preferred provider choice is not a production accuracy score.

Example

PP-DocLayoutV3 is the normal table-region provider at threshold 0.50. That statement is a current-contract and implemented claim. Table accuracy remains unknown until representative fully reviewed pages are measured. That accuracy statement is not validated.

Open Questions

• Should product UI reuse these four words exactly, or keep shorter user-facing copy?

Sources

• Current contract: table-dimension-detection-architecture.md (2026-08-12), Validation gates
• Wiki surface plan: 260814_drawing-lab-wiki-surface/README.md (plan draft)