The public ToolboxMD Project directory for people and agents. Production is served at https://toolbox.md.
The website is generated from released Project and distribution facts:
.toolboxmd/projects.jsonowns Project-to-website mappings only.- each Project Record owns Project identity and fact locations;
- ToolboxMD Marketplace owns released Agent Module distribution evidence;
scripts/site_pipeline.pyresolves, generates, validates, and verifies the exact public representation.
Build the complete Website Candidate from exact released local inputs. Follow
GitPix input preparation
for approved read access and the activation metadata bundle. Check out GitPix at
the resolver's exact source_sha, with its release tag available. The Marketplace
release and the AgentsMD release it names must also be checked out exactly.
The builder rejects source identity mismatches and missing GitPix inputs.
python3 scripts/site_pipeline.py build \
--project-root . \
--agentsmd-root .inputs/agentsmd \
--marketplace-root .inputs/marketplace \
--gitpix-root .inputs/gitpix \
--gitpix-inputs .inputs/gitpix-release.json \
--output dist/site \
--receipt dist/website-parity-candidate.jsonRun the deterministic proof suite:
python3 -m unittest discover -s tests -v
python3 scripts/site_pipeline.py validate \
--output dist/site \
--receipt dist/website-parity-candidate.jsonThe GitHub Actions workflow resolves the latest published Marketplace release, checks out the exact AgentsMD source commit named by it, and resolves the latest trusted GitPix activation and its exact released source. It builds both Projects in one isolated directory. Production deployment requires the Agent Module pilot closures and the GitPix first-publication gate. A scheduled run compares the expected and live site manifests, deploys only when stale, and emits a Website Parity Receipt after Live Verification.
See website delivery for the Cloudflare Pages seam, ownership boundaries, credentials, failure behavior, and discovery contract.