Two open questions surfaced while reviewing the host apply loop (during the controller/host-split discussion), each a design gap rather than an incident:
065 — a permanently-failing resource is retried for ever with no escalation. The reconcile loop is right for transient failures but makes a permanent one silent-in-the-way-that-matters: a machine looks busy (up, reconciling) while a resource inside it has never once applied, and nothing distinguishes "stuck for a week" from "failed a minute ago" without someone running push --behind.
066 — a partly-applied declaration leaves a mixed state with no rollback. Harmless for independent resources (deliberately so, per 04-ISSUES/011), unexamined for resource pairs that are only correct together, where gating doesn't apply and a half-state can be internally inconsistent.
Both are status: open, located-in: [], no fix proposed — diagnosis is a separate step. Checks (records, index, cycle) pass.
Two open questions surfaced while reviewing the host apply loop (during the controller/host-split discussion), each a design gap rather than an incident:
- **065** — a permanently-failing resource is retried for ever with no escalation. The reconcile loop is right for transient failures but makes a permanent one silent-in-the-way-that-matters: a machine looks busy (up, reconciling) while a resource inside it has never once applied, and nothing distinguishes "stuck for a week" from "failed a minute ago" without someone running `push --behind`.
- **066** — a partly-applied declaration leaves a mixed state with no rollback. Harmless for independent resources (deliberately so, per 04-ISSUES/011), unexamined for resource *pairs* that are only correct together, where gating doesn't apply and a half-state can be internally inconsistent.
Both are `status: open`, `located-in: []`, no fix proposed — diagnosis is a separate step. Checks (records, index, cycle) pass.
Surfaced while reviewing the host apply loop for the controller/host
split discussion. 065: a permanently-failing resource retries for ever
with no escalation — reported, but never raises its hand as stuck.
066: a partly-applied declaration leaves a mixed state with no rollback,
which is harmless for independent resources and unexamined for pairs
that are only correct together. Both are questions HQ must answer, not
incidents — status open, no fix proposed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Two open questions surfaced while reviewing the host apply loop (during the controller/host-split discussion), each a design gap rather than an incident:
push --behind.Both are
status: open,located-in: [], no fix proposed — diagnosis is a separate step. Checks (records, index, cycle) pass.