Implement TENSOR Core in 30 Minutes

30-Minute Core Implementation Path

This path is for teams integrating TENSOR as a shared investigation contract. Completion criteria are explicit so implementation claims remain verifiable.

Step 1: Pin Release Artifacts

• Schema: core.schema.json
• Graph: tensor-core.json
• Release manifest: releases/manifest.json

Expected output: your integration references explicit graph and schema versions.

Step 2: Validate Contract

• Run schema validation on canonical graph artifacts.
• Fail your build on structural violations and edge ID mismatches.
• Document accepted version range in your implementation README.

Expected output: deterministic pass/fail validation stage in CI.

Step 3: Run Conformance Fixtures

• Manifest: conformance/manifest.json
• Valid fixture: core-minimal.json
• Invalid fixture: edge-id-mismatch.json

Expected output: valid fixture is accepted, invalid fixture is rejected with explicit error details.

Step 4: Enforce Deterministic Execution

• Map runtime transitions to yes, no, or unknown only.
• Store traversal state with stable node and edge IDs.
• Keep model-generated reasoning as evidence, not branch policy.

Expected output: replayable traversal records for audits and debugging.

Done Criteria

• All required fields validate against pinned schema.
• Conformance fixtures pass/fail as expected.
• Runtime traversal produces deterministic branch transitions.
• Implementation documentation states supported versions and extension behavior.

FAQ

Can we implement partially?

Yes. Start at Consumer tier and publish current tier coverage. Incrementally move to Executor and Authoring Tool tiers.

Can we keep platform-specific metadata?

Yes. Use namespaced extensions and keep core semantics unchanged.

Implement next: Conformance Suite · Standards · Contribute updates