PixieCore decision log
Decision records preserve why durable project choices were made. They are not a replacement for implementation documentation or issue discussion.
When a record is required
Create a record for normative POP changes, public compatibility changes, security or trust-boundary decisions, long-lived architecture constraints, governance amendments, and maintainer membership changes.
Lifecycle
- Copy
0000-template.mdto the next four-digit number and a short lowercase slug. - Set the status to
proposedand link the supporting issue or pull request. - Record participants, disclosed conflicts, alternatives, evidence, and compatibility impact before a final decision.
- Set the status to
acceptedorrejectedwhen the decision is made. - Never rewrite an accepted decision to change its meaning. Add a new record
with status
supersedesand cross-link both records.
Valid statuses are proposed, accepted, rejected, superseded, and
withdrawn.
Records
| ID | Status | Decision |
|---|---|---|
| 0001 | accepted | Establish public project governance and decision records |
| 0002 | accepted | Adopt the POP specification change process |
| 0003 | accepted | Keep deferred execution outside the core runtime |
| 0004 | accepted | Defer a hosted Blueprint registry |
| 0005 | accepted | Keep PixieCore self-hosted in 0.1 |
| 0006 | accepted | Compose the locked foundation with a Recipe |
| 0007 | accepted | Remove the redundant preset layer |
| 0008 | accepted | Co-locate Recipe with bundled plugins |
| 0009 | accepted | Group repeated production source prefixes |
| 0010 | accepted | Use fractal directory ownership at every level |
| 0011 | proposed | Restore prompt-first POP on the 0.2 development branch |