Get in touch
For evaluation, governance discussion, or upstream integration work. (In)Canon is a protected methodology and product. Disclosure is scoped to what is necessary.
(In)Canon does not establish truth, correctness, quality, compliance, or adequacy. It reports only whether required structural elements are explicitly stated or not stated. Evaluation can be performed at the interface and artefact level without access to internal mechanics.
1) Evaluation
- You want to assess (In)Canon outputs and determinism.
- You want to test it against your data (or safe proxies).
- You need a clear boundary between stated evidence and supplied structure.
2) Integration
- You want (In)Canon upstream of an LLM, scoring model, or workflow tool.
- You need a gate contract, presence/absence semantics, and fixtures.
- You have constraints (PII, on-prem, audit logs, procurement).
3) Research / governance collaboration
- You are working on assurance, defensibility, audit trails, or evidence synthesis.
- You want the reconstruction/interpretation boundary made explicit.
- You need a method-oriented discussion rather than a product pitch.
What to include
- Your domain (health, audit, legal, governance, research, etc.)
- Where reconstruction risk appears in your workflow
- Desired next step (call, evaluation, integration sketch)
- Constraints (security, compliance, environment)
Discussable without NDA
- Interface contract (inputs, outputs, versioning)
- Determinism and testability properties
- Presence/absence semantics (“stated” vs “not stated”)
- Integration patterns (hard gate vs constrained continuation)
- Audit artefacts and logging expectations
Requires NDA (scoped)
- Internal rule sequencing and logic
- Protected lexicons, matching methods, or thresholds
- Implementation detail not necessary for interface evaluation
- Any material that would enable reproduction of internal mechanics
Most organisations can evaluate (In)Canon at the interface level first. Deeper access is conditional, limited, and justified by a concrete engagement need.
Copy, edit, and send:
Subject: (In)Canon enquiry — [Evaluation / Integration / Research]
Hi David,
I’m contacting you from [organisation / team]. Our domain is [domain].
Use case:
- Where reconstruction risk appears: [brief description]
- What we are trying to prevent: [silent assumptions / defensibility gaps / overconfident automation]
- Intended downstream: [LLM / scoring / audit report / synthesis / other]
Constraints:
- Data sensitivity / environment: [PII / on-prem / offline / other]
- Governance / compliance needs: [brief]
What we’d like next:
- [short call / interface-level evaluation / integration sketch / other]
Best,
[Name]
[Role]
[Organisation](In)Canon identifies structure and reports stated vs not stated. It does not assess meaning, correctness, quality, compliance, or adequacy.