Green-lane part of AWQ-013. Scanned 117 git repos.
Inverts the framing: ownership is not undetermined. LICENSE §2 (TRSL V1C1)
already names Binky Hedgehog GmbH as Licensor 'holding the rights necessary'
on 104 repos. The question is whether that published assertion is documented —
no assignment, Einbringung, or service contract with an IP clause exists
anywhere in the estate. May be in 2binky or the 2019 formation papers; that
founder check is step 1 and gates G5/G6.
Two further gaps: TRSL depends on a Phase Manifest and no manifest instance
exists in any repo (only spec+schema in target-revenue), so the licence
identifies no Software, target, or future licence; and 12 repos have no LICENSE
at all while railiance-bootstrap asserts a third party.
Funding-source column blocked on AWQ-002.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Found by the UPC-WP-0002-T04 residual sweep. The Reactivation Plan calls this
'needed before selling ecosystem products' but nothing owned it — it was an
unchecked checklist box with no work record, and it gates G5/G6.
Distinct from AWQ-002 (which assembles IP evidence from Eigenentwicklung
invoices); this is the ownership determination that consumes that evidence.
Inventory table is green-lane; the allocation/transfer itself is Red.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Align AGENTS, AutonomyPolicy, SCOPE, OperatingRhythm with fleet residual
role (live intakes, not SCOPE prose). Capture BINKY-WP-0006 leftovers as
AWQ-011 (brief-weekly) and AWQ-012 (open-weights retarget).
Convention change, not new code: closing an item now means setting its
terminal status (status: closed/resolved/done + outcome where
applicable) directly on the item's own yaml block in place, instead of
deleting it and hand-writing a bullet in a separate "Completed"/
"Resolved decisions" log. WORK-RECORDS.md (CUST-WP-0061-T04, generated
by fix-consistency's C-33) already lists every closed/resolved/done
record with status/lane/source -- that supersedes the hand-maintained
logs as the going-forward view.
- AutopilotWorkQueue.md: closing note added; "## Completed" relabeled
"(historical -- pre-canon, 2026-07-21)", frozen as-is, nothing
migrated or deleted
- DecisionQueue.md: closing note added -- its "## Resolved decisions"
entries were already structured as in-place yaml blocks with
status: resolved (ahead of AWQ's convention already), so this only
clarifies the log is superseded going forward, no structural change
- OfficeHourQueue.md: closing note added -- items already live under
"## Queued items" with status: queued|prepared|done in place, no
separate log ever existed here
- OperatingRhythm.md: queue-hygiene checklist updated to describe
in-place status transitions instead of "moved to the log"; added
item 5 noting WORK-RECORDS.md needs no hand-maintenance
Re-ran fix-consistency: WORK-RECORDS.md content unchanged (correctly
idempotent -- these were prose-only edits, no yaml block content
changed).
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Live verification of the new fix-consistency C-32 check
(state-hub CUST-WP-0061-T02): AWQ-002, AWQ-003, AWQ-006 were open,
never-registered intake items in AutopilotWorkQueue.md. C-32 created
real hub intake records for each and wrote state_hub_intake_id back —
the exact registration gap the work-record canon was built to close,
caught on real, non-synthetic data on its first run.
(A throwaway BINKY-IN-9001 test block used to trigger this run was
never git-tracked and has been removed from disk; its hub record was
closed declined as cleanup.)
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
- E-mail triage log section added: jamesandersons spam resolved by
founder; IHK Sommerfest invitation (August, founder calendar call);
Qonto MCP mailing -> actionable
- AWQ-010: Qonto MCP integration prep (read scopes first, ops-warden/
OpenBao credential lane, no native integrations; complements DUO =
DATEV Unternehmen Online as main accounting, does not replace it)
- OH-2026-003 enriched: MCP integration is an argument FOR keeping
Qonto; check API/plan prerequisites while in the dashboard
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
DNS for api.preprod.blobr.dev (and blobr.dev) no longer resolves; Stripe
has sent monthly failure digests since April. Deletion is a founder
dashboard action, prepared as OH-2026-005 incl. webhook-endpoint
inventory while in the dashboard.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Scan c3c7e784 via warden/OpenBao lane, evidence CSV in mailmeta/reports/
(metadata only; sqlite state gitignored). Checklist item 8 done. New
AWQ-009: Stripe webhook delivery failure noticed 2026-07-05 — first
real-world event caught by the lane. Two suspicious external mails
logged, not acted on.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Evidence from 2binky archive: FSW DATEV pass-through 483,69 EUR/yr, HUB31
desk contract renewed to 2027-04, private-card company costs (bubble.io,
AI subs), open 450 EUR Binect receivable. Audit corrected: desk landlord
is HUB31; Binect is income side.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Company-agnostic flagship-offer template generalized from the Binky
dogfood run. audit-core assessed as home candidate — it owns audit event
logging, not company audits, so the template stays in binky-control.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
OperatingRhythm.md (daily brief format, queue hygiene, weekly review),
AutopilotWorkQueue.md seeded with 6 evergreen items, first daily brief
written for 2026-07-16.
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
