KFD Candidates
KFD Candidates preserve potentially load-bearing portable engineering rules before a KFD number is allocated. They are pre-number drafts, not numbered decisions.
The machine source is registry.json. A candidate may carry
a non-binding slotHint to preserve the current ordering hypothesis. The hint
does not reserve, allocate, or promise that number. Only an explicit promotion
creates a numbered KFD under decisions/ and registry.json.
candidate
-> qualification
-> explicit promotion
-> numbered draft
-> activation evidence
-> active KFD
Candidates may be revised, reordered, merged, split, withdrawn, rejected, or promoted while their published coordinates remain immutable. Their current status and claim boundary must remain machine-readable.
Any participant may propose a candidate, counterexample, adopter Profile, or
qualification evidence through the public process in
CONTRIBUTING.md. Maintainers remain responsible for
official numbering and status decisions.
Promoted lineage:
- Cross-domain action primitives was explicitly promoted into active KFD-7.
- Atlas action perspective was explicitly promoted into numbered draft KFD-8.
- Pursuit intent continuity was explicitly promoted into numbered draft KFD-9.
- Warrant bounded authority was explicitly promoted into numbered draft KFD-10.
- Claim, Assessment, Decision, and Admission was allocated to numbered draft KFD-11 by the 2026-07-21 pre-stable Foundation Revision.
Incubating now:
- Federated Work Continuity asks whether one user-level body of work remains independently identifiable across the Assignments, workspaces, and cuts through which it advances. Its strongest alternatives remain Initiative, a perspective-bound derived view, and no new Primitive.
The promoted pages remain public lineage and do not replace their numbered decisions. Incubating pages are non-normative and allocate no number.
See Contributing and Governance for open proposal, candidate promotion, pre-stable Foundation Revision, stewardship, and Foundation Freeze rules.