Issues

Let a leaf read a person's own text against their data slots

human-centric-engineering/daybreak#295 · opened

on Oct 6, 2026

Tell which unique index a write hit when Prisma runs through the driver adapter

human-centric-engineering/daybreak#294 · opened

on Oct 6, 2026

Give leaves a place to keep a person's journey record: entries they can edit and remove

human-centric-engineering/daybreak#293 · opened

on Oct 6, 2026

Give leaves a writer for session events in the journey event stream

human-centric-engineering/daybreak#292 · opened

on Oct 6, 2026

Module admin page: no seam for a leaf to add its own tab

human-centric-engineering/daybreak#289 · opened

on Oct 4, 2026

Data slots: the AI is never told which slot names exist, so it invents new ones

human-centric-engineering/daybreak#288 · opened

on Oct 4, 2026

Let a facilitation agent find what a person said by meaning, in their conversations only

human-centric-engineering/daybreak#287 · opened

on Oct 3, 2026

2

Let a person remove one slot value without breaking version numbering

human-centric-engineering/daybreak#286 · opened

on Oct 3, 2026

1

Boundary vocabulary scan has no leaf seam: a leaf's own route group is always "core"

human-centric-engineering/daybreak#285 · opened

on Oct 1, 2026

Re-registering a module at runtime changes it for every org and every request on that server

human-centric-engineering/daybreak#284 · opened

on Sep 29, 2026

1

Module admin page never shows the module's own data slots (no Slots tab, and no scope filter on the slot list)

human-centric-engineering/daybreak#281 · opened

on Sep 25, 2026

1

Data slots: special_category masking covers the value but not the reasoning note, so Art. 9 prose can land at rest

human-centric-engineering/daybreak#269 · opened

on Sep 21, 2026

1

Data slots: an open-mode mint is always `standard`, so special_category masking is unreachable on the only path a conversation can write

human-centric-engineering/daybreak#268 · opened

on Sep 21, 2026

2

Data slots: admin can read any user's slot values with no seam for the user's own consent

human-centric-engineering/daybreak#267 · opened

on Sep 20, 2026

2

Leaf apps have no way to register global (non-module) slot definitions

human-centric-engineering/daybreak#266 · opened

on Sep 19, 2026

Facilitation role route: a leaf hook around the turn (turn id, cost/message metadata, refuse-or-replay)

human-centric-engineering/daybreak#265 · opened

on Sep 18, 2026

5

framework:changelog fails every leaf PR that fills a lib/app/* seam — the surface rules are Daybreak-repo rules running in a leaf

human-centric-engineering/daybreak#258 · opened

on Sep 14, 2026

/pre-pr's advisory sends a leaf to fill lib/app/ci.ts — a bridge — instead of lib/app/leaf-ci.ts

human-centric-engineering/daybreak#257 · opened

on Sep 11, 2026

1

Two journey-table writers are exported to leaves with a caller-supplied subject and no access predicate

human-centric-engineering/daybreak#251 · opened

on Sep 11, 2026

1

defaults.test.ts: filling a leaf-* seam breaks the BRIDGE's row, which the leaf guide's rule doesn't cover

human-centric-engineering/daybreak#234 · opened

on Sep 8, 2026

2

facetAllows has no slug-level facet, and module capabilities do not inherit exposure enforcement

human-centric-engineering/daybreak#169 · opened

on Jul 27, 2026

1

Data slots: capability writes (fill_slot) carry no run context, so an agent-captured value can never join a run's picture

human-centric-engineering/daybreak#167 · opened

on Jul 25, 2026

2

Module config: array fields fall back to a raw JSON editor, so a module whose config IS its content can't be edited by its owner

human-centric-engineering/daybreak#161 · opened

on Jul 25, 2026

Data slots: runId provenance and a batched history read (all versions, optionally by run)

human-centric-engineering/daybreak#156 · opened

on Jul 24, 2026

4

Navigation Menu

Repository navigation

Issues

Let a leaf read a person's own text against their data slots

Tell which unique index a write hit when Prisma runs through the driver adapter

Give leaves a place to keep a person's journey record: entries they can edit and remove

Give leaves a writer for session events in the journey event stream

Module admin page: no seam for a leaf to add its own tab

Data slots: the AI is never told which slot names exist, so it invents new ones

Let a facilitation agent find what a person said by meaning, in their conversations only

Let a person remove one slot value without breaking version numbering

Boundary vocabulary scan has no leaf seam: a leaf's own route group is always "core"

Re-registering a module at runtime changes it for every org and every request on that server

Module admin page never shows the module's own data slots (no Slots tab, and no scope filter on the slot list)

Data slots: special_category masking covers the value but not the reasoning note, so Art. 9 prose can land at rest

Data slots: an open-mode mint is always `standard`, so special_category masking is unreachable on the only path a conversation can write

Data slots: admin can read any user's slot values with no seam for the user's own consent

Leaf apps have no way to register global (non-module) slot definitions

Facilitation role route: a leaf hook around the turn (turn id, cost/message metadata, refuse-or-replay)

framework:changelog fails every leaf PR that fills a lib/app/* seam — the surface rules are Daybreak-repo rules running in a leaf

/pre-pr's advisory sends a leaf to fill lib/app/ci.ts — a bridge — instead of lib/app/leaf-ci.ts

Two journey-table writers are exported to leaves with a caller-supplied subject and no access predicate

defaults.test.ts: filling a leaf-* seam breaks the BRIDGE's row, which the leaf guide's rule doesn't cover

facetAllows has no slug-level facet, and module capabilities do not inherit exposure enforcement

Data slots: capability writes (fill_slot) carry no run context, so an agent-captured value can never join a run's picture

Module config: array fields fall back to a raw JSON editor, so a module whose config IS its content can't be edited by its owner

Data slots: runId provenance and a batched history read (all versions, optionally by run)