Skip to content

Latest commit

 

History

History
87 lines (65 loc) · 4.08 KB

File metadata and controls

87 lines (65 loc) · 4.08 KB
type Reference
title Iteration vocabulary
description Identifier glossary and work-queue field schema for OKF — not workflow rules or commands.
tags
testing
validation
workflow
work-queue
timestamp 2026-07-31 00:00:00 UTC

Iteration vocabulary

Glossary of string identifiers and work-queue field names used across OKF. This doc does not define procedures, gate rules, or Gradle commands — each topic has one owning doc; others link.

Policy: OKF documentation and commit policy.

Topic Owner
Change loop, gates, frozen tree change authoring workflow
All agent shell commands agent command policy
E2e-only detail, emulator, suite scope running e2e
Validation command sequence validation checklist
Work-queue gate snapshots Module/area work queues (ephemeral)

Work type identifiers

Work type Brief meaning
gap-analysis Read-only feasibility / semantics check
baseline-capture Record before snapshots or baselines
implementation Author product code and tests
independent-review Verify a frozen diff
documentation User docs and durable OKF updates
commit Stage and create one commit
pre-merge-validation Branch-wide merge gate

When to use each work type, validation tier, edit policy, and commit rules: change authoring § work types.

Validation tier identifiers

Tier id Brief meaning
unit-focused Fast validation while product code is changing (module-scoped unit tests; optional focused e2e)
area-focused Full loaded module/area suite for the change (module unit tests + e2e when Auth UI/emulator path touched)
full Unfocused — CI unit path + e2e when Auth is in scope

E2e scope and rules: change authoring § validation tiers, running e2e.

Gate identifiers

Work queues use these field names (values: open | closed):

Field Tracks
implementation_gate implementation work type complete
review_gate independent-review work type complete
commit_gate Durable commit exists for the item after prior gates closed with validation evidence

What closes each gate, trust rules, and loop transitions: change authoring § gates.

commit_gate closes when a durable commit exists whose subject matches the row's commit_subject, after implementation_gate and review_gate closed with validation evidence.

Items may also be marked blocked when a dependency gate is open elsewhere.

Work-queue fields

Ephemeral work queues may record:

Field Allowed values / meaning
next_work_type A work type identifier
validation_tier unit-focused | area-focused | full
module Optional Gradle module scope (e.g. auth, firestore)
implementation_gate open | closed
review_gate open | closed
commit_gate open | closed
commit_subject Planned or landed first line of the item's focused commit (Conventional Commits subject). Set before git commit; must match the commit that closes commit_gate. Do not record SHAs.
blocked Item or dependency blocked until named gate closes

Queues record state, not who executes the work.

Related docs

Topic Document
Change authoring loop change-authoring-workflow.md
E2e commands running-e2e.md
Validation commands validation-checklist.md
Doc/commit policy documentation-policy.md