Library / Put the work to use

Find it. Understand it.
Make useful progress.

The Library connects independent projects, research and reusable capabilities. Start with the reader’s job, resolve the owning source and its actual state, then use that project’s instructions. A catalog entry is not a runtime or an installation promise.

1. Find the right Work

Browse and filter the catalog, or use the existing Library CLI from a checkout. Search returns compact matches; inspect takes an exact slug or stable Work ID.

node bin/gls search "agent runtime"
node bin/gls inspect siso-agent-base

The dossier gives the selected Snapshot and Release, artifact locators, ownership, source visibility and entry instructions. If commands have not been reviewed, it says so. gls refuses a stale generated projection and tells you to rebuild it; it does not silently treat yesterday’s output as current.

2. Read the owner’s entry before execution

Use the Work’s For agents entry and the pinned source. Keep private access, installation, runtime admission and production qualification separate. Action Model owns its assembly methods; Harness Lab owns improvement experiments; Project OS owns the reusable task and execution lifecycle.

For remote reading, llms.txt is the short router and catalog.json is the generated machine catalog. Each Work links to a bounded dossier rather than asking an agent to reconstruct the whole library.

3. Take a bounded, checkable task

node bin/gls tasks
node bin/gls task TASK-0007

These read the existing .agents/tasks/ records. The task contains its scope, acceptance criteria and evidence. It does not claim itself, start an agent or grant publication authority. For work in another project, use that project’s existing task and handoff system.

Record the input/source revision, exact changed files, checks and exit codes, result and remaining gate. A repeated attempt with no changed input or new evidence is a reason to revisit the task or report a blocker, not call the same failure a success.

Current Library work

This is a build-time projection of the existing task records, not a live agent feed or another task writer. Read the scope and acceptance before acting. A blocked task needs its blocker resolved; a completed task is evidence to inspect.

TASK-0003 · Publish a successor Event recording the honest 8-of-13 delivery backlog

The immutable launch Event records the program as launched. No record states what actually landed. Write a SUCCESSOR Event naming lanes 5, 6, 9 and 12 explicitly.

  • A successor Event exists naming lanes 5, 6, 9 and 12
  • The immutable launch Event is unmodified and check:immutable still passes

Last recorded step: 2026-09-08T06:32:26+07:00 · Reviewed remaining acceptance and repeat-work boundary

node bin/gls task TASK-0003 · Read-only task projection

Canonical source: .agents/tasks/backlog/TASK-0003/task.json

TASK-0004 · Own the missing convergence step: the adversarial release gate backlog

Prompt 13 evaluates COMPATIBILITY; v0 Prompt 12 would have PROVEN the P0s fixed and published the closing Event. The spec survives and is reusable. Nobody currently owns final convergence.

  • An owner is named for the release gate
  • Prompt 1's original failure fixtures are run and the selected P0s proven resolved
  • No red gate is papered over

Last recorded step: 2026-09-08T06:32:26+07:00 · Reviewed remaining acceptance and repeat-work boundary

node bin/gls task TASK-0004 · Read-only task projection

Canonical source: .agents/tasks/backlog/TASK-0004/task.json

TASK-0005 · Pre-register a GQ-010 baseline BEFORE merges change the graph blocked

GQ-010 has no baseline, so nothing downstream of it is measurable. This is TIME-CRITICAL in a way the other tasks are not: once the merges land, today's graph is gone and the before-picture cannot be reconstructed.

  • 5 decisions pre-registered with their measurement protocol frozen before the first timing
  • Timings recorded against the pre-merge graph
  • The registration is timestamped outside the analyst's own control

Last recorded step: 2026-09-08T06:32:26+07:00 · Reviewed remaining acceptance and repeat-work boundary

node bin/gls task TASK-0005 · Read-only task projection

Canonical source: .agents/tasks/blocked/TASK-0005/task.json

Completed and cancelled records
TASK-0001 · Merge the People Graph control-plane spine completed

The spine carries ADR-0005, the Works and Releases records, V37, GQ-010 and the pg-observation-0.1 interchange format. It is the control plane the rest of the program hangs off.

  • npm run check:immutable passes
  • npm run verify passes
  • No immutable record is modified

Last recorded step: 2026-09-08T06:32:26+07:00 · Reconciled completed work against canonical main

node bin/gls task TASK-0001 · Read-only task projection

Canonical source: .agents/tasks/completed/TASK-0001/task.json

TASK-0002 · Merge the three docs-only branches completed

Three documentation branches with no conflict risk. The audit record holds findings PG-AUDIT-001 to 013, each pinning exact blob revisions, plus a 509-line complete-decision-record. Source research holds the 39-source matrix, rights and deletion matrix, 10 value theses and the pilot portfolio. First-principles holds R1-R10 and the value function.

  • All three merged
  • The prompt packs are reachable from main

Last recorded step: 2026-09-08T06:32:26+07:00 · Reconciled completed work against canonical main

node bin/gls task TASK-0002 · Read-only task projection

Canonical source: .agents/tasks/completed/TASK-0002/task.json

TASK-0006 · Register the three split repositories as Works completed

The Work records for siso-unsolveable-mathematics, siso-stargate-library and siso-declassified-records are written and pushed but not merged.

  • The branch is merged and validate still passes

Last recorded step: 2026-09-08T06:32:26+07:00 · Reconciled completed work against canonical main

node bin/gls task TASK-0006 · Read-only task projection

Canonical source: .agents/tasks/completed/TASK-0006/task.json

TASK-0007 · Integrate the shared Library reading frame for review completed

A locally verified shared reading flow with exact source pins, preserving public identity and original reader content. Public publication is a separate gate.

  • Node 20 full Library gate and strict integration diagnostic pass.
  • Every generated HTML route has one shared navigation and main landmark, working local anchors and source parity.
  • Representative desktop/mobile, keyboard, storage-denied and no-JS browser checks pass.
  • Public hosts and peer checkouts remain unchanged.

Last recorded step: 2026-09-08T03:16:39.321493+00:00 · Owner accepted the bounded integration and canonical release

node bin/gls task TASK-0007 · Read-only task projection

Canonical source: .agents/tasks/completed/TASK-0007/task.json

TASK-0008 · Provide safe read-only discovery, inspection and task entry through gls completed

Make a cold agent able to resolve source state and owning entry through the existing Library CLI and read canonical task scope without assembling several projections by hand.

  • Focused Node 20 read/add contract suites pass.
  • Real current-registry search/inspection returns the selected Runtime source and correct private/unselected Harness boundary.
  • A cold lower-capability reader can use the commands and return a checkable source receipt.
  • No input mutation or public deployment is performed.

Last recorded step: 2026-09-08T09:47:34+07:00 · Owner accepted bounded implementation

node bin/gls task TASK-0008 · Read-only task projection

Canonical source: .agents/tasks/completed/TASK-0008/task.json

TASK-0009 · Author a source-backed Runtime entry through the Library operating path completed

Use gls discovery and exact Work inspection to identify the selected SISO Agent Runtime source, read its public owning instructions, and add useful authored reading content without changing identity or source claims.

  • Resolve Runtime through gls search and exact inspect; preserve its existing stable ID and legacy slug.
  • Read the exact selected public source README and relevant command definitions before authoring.
  • Change only reading, updated_at and appended source-review evidence in registry/works/siso-agent-base.json.
  • Three useful real source links and actual documented commands; no invented runtime, rights, private-access or cost claims.
  • Registry validation passes and the Library owner independently reviews source/record parity before acceptance.

Last recorded step: 2026-09-08T09:47:34+07:00 · Owner accepted bounded implementation

node bin/gls task TASK-0009 · Read-only task projection

Canonical source: .agents/tasks/completed/TASK-0009/task.json

4. Contribute reviewed metadata

Read and classify source first. Prepare a schema-valid record and inspect a dry run before a real add:

node bin/gls add work --file candidate-work.json --reviewed-public --dry-run
node bin/gls add work --file candidate-work.json --reviewed-public

The real command holds an exclusive lock and runs the Library gate. Failed adds roll back only unchanged files created by that invocation. Existing records are never overwritten by add; changes to current Work metadata are reviewed source edits, while accepted immutable records require successors. Read the exact CLI contract.

5. Upgrade once, verify each consumer

The shell and its components stay in their owning source repository. Review an exact source revision, register a Release with its evidence, select it in a successor Snapshot, and pin the consumer to the same revision. The build copies those assets. This gives projects a common source without making every live deployment change unexpectedly.

node scripts/audit-ui-integration.mjs --strict
npm run verify

The diagnostic checks source and selection; the full gate checks registry, generated routes and publication safety. Actual browser behavior and live deployment need their own receipts. Integration contract and acceptance.

The operating system behind the work

Open the owning project.

projectactive

SISO Project OS

A project-local operating system and contract bundle for durable agent work, evidence, knowledge, and handoff state.

Selected release

gls:work:54a52e52-dfbd-4922-8c04-ec02f7fae943
applicationactive

SISO Agent Runtime

The provider-neutral SISO coding-agent application boundary: explicit configuration, safe host launch, profile composition, task control, checkpoints, bounded context, status, and runtime event contracts.

Selected release

gls:work:b584bbf7-acde-46a2-b33e-e430ee1df224
capability_packactive

SISO Skills

The registry and distribution boundary for atomic repeatable capabilities, with evidence-backed classification, bundled installation, isolated skill telemetry, and independent repository promotion only when a skill earns its own lifecycle.

Selected release

gls:work:8acb11e9-026f-47e3-b620-bb1b969bcbcd
toolexperimental

SISO Shell

The shared CRM-derived navigation, reusable page parts and static template bank for SISO reading surfaces. Consumers pin an exact source revision and supply reviewed project data; a template example is not a current project observation.

Selected release

gls:work:dd051ce3-520e-4799-87b0-1e3f2182cc72
projectactive

SISO Harness Lab · Agent Effectiveness

An evidence-gated improvement project for better accepted outcomes at comparable compute, or preserved quality at lower cost. It keeps experiments, counterexamples, rejected changes and continuation state. Private source; no established equal-spend quality gain, automatic instruction promotion or general cost multiplier.

Registered · not selected · includes private source

gls:work:1cc4c944-9351-466e-a442-9fe16ad145d1
projectactive

Action Model · SISO Agency Assembly Framework

Reusable methods for agents to assemble software from existing capabilities, bounded adaptation and verification, with a public human/agent Blueprint and a private owning source. Public metadata only; registration does not admit source payload or prove a production integration.

Registered · not selected · includes private source

gls:work:9ab07516-c02c-4798-857a-2eb8d1d2edfa