Issues are grouped by the layer they affect, making it easier to understand which part of the system each problem belongs to.
Concepts carrying app concerns, conflation of identity spaces, global mutable state, and Publishing non-atomicity.
Stage gating, failure propagation, dev overlaps, registration-order sensitivity, and missing rebuild triggers.
Evidence matching, frame query determinism, failure isolation, and registration semantics.
Binary asset corruption and content-type edge cases.
Regex-based template parsing, CLI argument validation, frontmatter detection, and mode validation.
Each issue page keeps the same shape:
The findings cluster around four themes.
| Theme | What it means |
|---|---|
| Concept independence | Concepts should not carry app-specific template or runtime semantics. |
| Sync gating | Success actions must not run just because they appear later in a then list. |
| Engine determinism | Matching, consumption, ordering, and failure handling need sharper invariants. |
| Filesystem boundaries | Paths must be canonicalized before serving, writing, or deleting. |
Start with Concept Design for independence problems, or Engine Core for the deepest framework-level bugs.