Agents · application · active
SISO Agent Runtime
A small provider-neutral host boundary with explicit configuration, bounded context, checkpoints and status contracts.
The Library’s reading
Why it matters
Runtime gives a coding-agent host a deliberate application boundary: configure the executable and profile files explicitly, validate the setup, launch argv without a shell, and exchange durable checkpoint and status data. Its six internal modules describe a focused experimental contract rather than the broader Agent Base warehouse, so adoption still depends on the selected source revision and the host's own capabilities.
Read the reasoning & boundaries ↗How it links
Sauce
The useful things to open first. Claims stay attached to dated receipts.
Read the public boundary
The README defines the clean extraction, its six internal module responsibilities, the excluded domains, and the experimental 0.1.0 adoption limit.
Open source ↗02 / Source highlightInspect the machine contract
The manifest records provider neutrality, the Node CLI entrypoint, explicit JSON configuration, argv-only host launch, and each module responsibility.
Open source ↗03 / Source highlightTrace the command surface
The CLI source defines manifest, doctor, where, run with optional dry-run, checkpoint, compact and status, including their required input options.
Open source ↗For agents
SISO Agent Runtime maintainer · Start with the source entry, then the machine-readable dossier.
Documented entry commands: node bin/siso-agent-runtime manifest · node bin/siso-agent-runtime --help. These are documented source entry commands; fresh test results are recorded separately in the evidence. Follow the owning source instructions before execution; private access and campaign activation remain separate.
Repos & source links
Relationships
HerdrSISO Agent Runtime provides the coding-agent application boundary used within the stack; Herdr remains the independently owned persistent workspace substrate.
SISO Agent Base Source WarehouseThe retired Agent Base source warehouse is preserved as extraction provenance; it is not the canonical Runtime repository or a runtime dependency.
Evidence & receipts
Installer, launchers, runtime extensions, application surfaces, nested repositories, package manifests, repository size, and dirty state were read directly. The shippable center is an application/distribution; the surrounding repository is not one coherent Work.source-review:siso-agent-base-decomposition:2026-07-30
Clean provider-neutral Runtime foundation published with six internal module contracts, five passing behavior tests, publication checks, and explicit parity limits.repo-check:siso-agent-runtime:a4aefc0345f979d67b5b3fac2829364a1a9100b9
Pinned public README, runtime manifest, and CLI command definitions reviewed. The documented surface is an experimental Node.js 20+ provider-neutral launcher with explicit JSON configuration, checkpoints, deterministic context compaction, and machine-readable status; no feature parity or installation readiness beyond the selected release claims is inferred.Open receipt ↗
Provenance
- Work ID
- gls:work:b584bbf7-acde-46a2-b33e-e430ee1df224
- Registry source
- registry/works/siso-agent-base.json
- Origin
- siso
- License / redistribution
- MIT (verified)