technocore-conformance

Local-first conformance and interoperability infrastructure for the public protocol implemented by flop-labs/technocore-chat.

The harness is pinned to an inspected upstream revision in upstream.lock.json. It exercises observable behavior, rather than importing or depending on upstream internals, and rejects a checkout at any other revision before local checks can start.

This is an unofficial community project. It is not affiliated with or endorsed by FLOP Labs.

Safety boundary

Command	Target	Network/write boundary
doctor	disposable local upstream	starts a fresh local server only
check	disposable local upstream	executes C201-C306; never accepts a live target
mcp	local upstream MCP source	only sends stdio initialize and tools/list
inspect	explicit target	GET-only discovery; non-loopback targets must use HTTPS

check uses a temporary CHAT_ROOT; it never uses a persistent identity or writes to a deployed Technocore instance. Signed checks generate an in-memory Ed25519 did:key identity for each run and discard it when finished. inspect is compatibility evidence only, not authorization to mutate a deployment.

Requirements

• Python 3.12 and uv.
• A checkout of flop-labs/technocore-chat at the revision recorded in upstream.lock.json, as a sibling directory named technocore-upstream.
• On Windows, a provisioned WSL/Linux environment with uv; upstream uses POSIX-only functionality.

Install and run

For development, clone both repositories as siblings, then install this project's locked environment:

uv sync
uv run technocore-conformance doctor --upstream ..\technocore-upstream
uv run technocore-conformance check --upstream ..\technocore-upstream --with-mcp
uv run pytest

For a packaged installation, install the wheel with your Python package tool, then point doctor, check, or mcp at an explicit compatible upstream checkout.

Run checks and consume reports

check is the complete conformance run. It starts a disposable local upstream instance, runs C201–C307, and optionally C404 with --with-mcp. It never accepts a live target.

uv run technocore-conformance check --upstream ..\technocore-upstream --with-mcp `
  --format json --report .\artifacts\local-report.json

Terminal output may be text (default) or JSON. --report always writes the same stable JSON document atomically, with per-check status, duration, evidence, and PASS/FAIL/SKIP/ERROR totals; a non-passing run exits non-zero.

inspect is deliberately narrower: it sends GET requests only to /healthz, /.well-known/agent.json, and /openapi.json. It exposes no live-write command or profile and requires HTTPS for a non-loopback target.

uv run technocore-conformance inspect --target https://your-technocore.example --report .\artifacts\live.json

The MCP parity probe does not contact an HTTP target. It starts the supplied local MCP source only long enough to request initialize and tools/list, then verifies the published unsigned and signed tools; the signed-tool schemas must never accept private key material.

uv run technocore-conformance mcp --source ..\technocore-upstream\mcp

Reports and exit codes

Commands with --format json print a stable schema-versioned document. --report PATH writes the same JSON document atomically. Each report contains tool and schema versions, the selected target (when applicable), aggregate PASS/FAIL/SKIP/ERROR counts, and per-check evidence. A report containing any non-passing check exits non-zero. Argument errors exit with code 2; doctor reports local setup failures in its text output and exits non-zero.

Contributor identity

Public Technocore DID:

did:key:z6MksSVxPTwmyPq3dT64mfJvk7RTQ2noMB2q3Qobkqpfabrg

Project announcement:

https://x.com/neuronengineer/status/2093992332844495261

The DID is public identity material only. No private seed or persistent signing key is stored or required by this repository.

Verification and contribution

The CI workflow clones the upstream revision recorded in upstream.lock.json, then runs formatting, linting, type checking, the full test suite, and a wheel build/install smoke test on Linux. See CONTRIBUTING.md for local contribution rules and SECURITY.md for responsible disclosure.