Issues

report_auth_failure: optional consumer-supplied detail token for observation provenance

#26

· iceteaSA opened

on Aug 31, 2026

Contract: refresh-failure classification and the auth_events vocabulary, for consumers doing routing and backoff

#18

· iceteaSA opened

on Aug 29, 2026

Design discussion: an OpenCode plugin putting Claustrum on MAIN slots for providers with no dedicated auth plugin

#17

· iceteaSA opened

on Aug 29, 2026

verify-audit does not detect tail truncation — the stated contract is accurate, but absence-of-rows is not tamper-evident

#12

· iceteaSA opened

on Aug 25, 2026

Serve contract for claustrum-mode (auth plugins): 12 decisions needed before implementation

#9

· iceteaSA opened

on Aug 24, 2026

Serve path answers needs_reauth for a re-sealed capability on a pre-re-seal connection — connection/lease-scoped verdict suspected (insula#8 falsification hand-off)

#7

· iceteaSA opened

on Aug 18, 2026

Credential-usability clearing edge: the prefrontal router is now a named consumer — what is the intended way to observe unusable→usable transitions?

#6

· iceteaSA opened

on Aug 17, 2026

Multi-account custody: N accounts per provider now (non-rotating kinds), custody inversion later (rotating OAuth) — the one-refresher invariant made structural

#5

· iceteaSA opened

on Aug 14, 2026

Admin CLI vs running module: single-writer lease makes reads and mint-handle a consumer outage

#3

· iceteaSA opened

on Aug 8, 2026

Multi-account credentials per provider family: id convention + import sources (custody side of insula#1 GAP-1/2)

#2

· iceteaSA opened

on Aug 8, 2026

Cookie/opaque-payload credentials with external refresh (qwen-cloud class) + Linux runbook notes to contribute

#1

· iceteaSA opened

on Aug 8, 2026

Navigation Menu

Uh oh!

All issues

report_auth_failure: optional consumer-supplied detail token for observation provenance

Contract: refresh-failure classification and the auth_events vocabulary, for consumers doing routing and backoff

Design discussion: an OpenCode plugin putting Claustrum on MAIN slots for providers with no dedicated auth plugin

verify-audit does not detect tail truncation — the stated contract is accurate, but absence-of-rows is not tamper-evident

Serve contract for claustrum-mode (auth plugins): 12 decisions needed before implementation

Serve path answers needs_reauth for a re-sealed capability on a pre-re-seal connection — connection/lease-scoped verdict suspected (insula#8 falsification hand-off)

Credential-usability clearing edge: the prefrontal router is now a named consumer — what is the intended way to observe unusable→usable transitions?

Multi-account custody: N accounts per provider now (non-rotating kinds), custody inversion later (rotating OAuth) — the one-refresher invariant made structural

Admin CLI vs running module: single-writer lease makes reads and mint-handle a consumer outage

Multi-account credentials per provider family: id convention + import sources (custody side of insula#1 GAP-1/2)

Cookie/opaque-payload credentials with external refresh (qwen-cloud class) + Linux runbook notes to contribute

Uh oh!

Search results