Orbit is an Astro application for the DEV/Sanity Challenge Path One. It gives an agent and a human a shared research dossier: question, plan, evidence, claim-by-claim verification and an auditable answer. Its intended contribution is to show when the structure and conflict-aware entries of a Sanity Context Knowledge Base materially change an agent’s reasoning.
The public static surfaces are live:
The landing’s atom is interactive but separate from the research workflow. The observatory itself uses one central dossier with five URL-restorable views: Question, Plan, Evidence, Verification, Report. A browser agent can discover exactly ten WebMCP tools. It can submit a version-bound proposal, but it cannot claim human approval or overwrite an approved dossier.
Current delivery status: the static public application, Studio route and WebMCP registration are verified. The private Laravel gateway to Sanity Context is implemented and verified locally, but has not yet been deployed with its server-side organization Viewer token; public Context calls therefore return an explicit unavailable state. No challenge submission or claim of a completed comparative evaluation is made.
Start here: human walkthrough · current public deployment receipt · agent and baseline artifacts.
studio/— standalone Sanity Studio for projectpzscx4w8, datasetproductionweb/— Astro static site, Three.js orbital lab and Chrome MV3 side-panel packageservices/broker/— loopback-only Node broker and SQLite mission checkpointspackages/contracts/— shared mission, provider, budget, ActionCard and CCP contractspackages/core/— deterministic mission and budget logicpackages/providers/— fail-closed provider boundary and CCP handoff constructorfixtures/— public offline corpus and adversarial research fixturesdocs/— architecture, learning, research, gates, receipts and submission drafts
Prerequisites observed on 2026-09-21: Node 24.18.1, system npm 11.16.0, Git 2.51.0.windows.1. The reproducible lock was generated with npm 10.9.4; the repository pins that version and enables legacy peer resolution because the current Sanity and Vitest peer graphs otherwise trigger an npm Arborist failure.
npx --yes npm@10.9.4 install --legacy-peer-deps
npm test
npm run build --workspace @orbit/web
python tools/package_mv3.py
npm audit --omit=dev --audit-level=highTests and builds pass locally. The dependency audit still fails on high-severity transitive advisories in the standalone Sanity CLI/build graph, so this tree is not release-ready. Astro is pinned to 7.3.3 and Tailwind uses the supported Vite integration; the earlier Astro critical advisories no longer appear in the current audit.
The broker listens only on http://127.0.0.1:47831. Its basic health endpoint is GET /health. Browser requests are denied until Chrome's exact unpacked-extension origin is allowlisted. After loading web/dist, copy the 32-character extension ID from Chrome and start the broker from PowerShell with:
$env:ORBIT_ALLOWED_EXTENSION_ORIGINS = 'chrome-extension://<32-character-extension-id>'
npm run brokerThe broker validates this value strictly, echoes CORS only for the exact allowed origin, and continues to require its process-scoped bearer token for mutations. Private operations require authorization even from loopback command-line clients. The browser exchanges a single-use, five-minute association code for a scoped session; the process token is never sent to the page.
To load the side panel locally, build @orbit/web, run python tools/package_mv3.py to create the reproducible package, open Chrome's extension management page, enable developer mode, and load web/dist as an unpacked extension. This is a manual browser action; it has not yet been counted as a verified integration in this repository.
A reviewable snapshot is available at artifacts/orbit-companion-mv3-unpacked-build.zip; verify it against artifacts/SHA256SUMS.txt. It is an unpacked-development artifact, not a signed Chrome Web Store package.
studio/sanity.config.ts references the existing project pzscx4w8 and dataset production. The local Context-agent receipts record real initial_context and knowledge_base_read calls against Knowledge Base kb5CHIYGXCMJ; the agent keeps entry paths and SHA-256 digests in a pending dossier. The public browser must still reach the private Laravel proxy before those same reads can be demonstrated live. Four source cards are retrieved at static build time and are not presented as a replacement for Context.
- Web content, model output and tool output are untrusted by default.
- The browser bundle contains no cloud key.
- External adapters fail closed with
BLOCKED_EXTERNAL. - The physics experience is educational and is not a flight-dynamics model.
- Publishing, deployment, legal acceptance, spending and challenge submission remain human decisions.
See HUMAN.md for the continuation path and the gate model for evidence requirements.