Resource Center · Canine Development
Everything we know, and how we know it.
Essays, whitepapers, guides and system documentation for Assert, Assure, Assay and the Canine Code Analyzer behind them. Every article is versioned and signed by a named person, and every one that carries a number opens with the method behind it.
- v1 · 4.7k words28 October 2026
Paid to Measure, Never to Move the Number
How Canine Development keeps the CAI verdict out of every price: prices that never depend on the score, no remediation revenue, a build-enforced firewall between billing and scoring, and a calculation you can recompute yourself. Version 1.2.sha256706dff075b30c735…797ebcb4statusSigned - GuideAssert
Which gate to add first
A sequencing guide for CI gates: which check to enforce first, which to add next, and where the scheduled survey fits so quality holds without blocking a single merge. - DocumentationCCA/where-the-code-runs/
Where the code runs
The container, what we do to a repository, what leaves our machines.
Whitepapers
1Guides
9- GuideAssert
Which gate to add first
A sequencing guide for CI gates: which check to enforce first, which to add next, and where the scheduled survey fits so quality holds without blocking a single merge. - GuideAssay
The European Accessibility Act, and the evidence Assert gives you
The European Accessibility Act asks companies to declare that their websites and apps can be used by people with disabilities. Assert reads the evidence in your code at every survey, lists what to fix, and turns your declaration into a signed conformance report. - GuideAssay
The Cyber Resilience Act, and the evidence Assert gives you
See which Cyber Resilience Act requirements Assert gives you evidence for at every survey, from the list of components (SBOM) and known vulnerabilities to secrets and build provenance, and get the rest ready for the people who declare it before December 2027. - GuideAssert
Set your survey cadence, and the daily watch
The two schedules Assert runs on: the sprint-cadence survey and the daily security watch. What each one checks, how to configure them, and how to tell a clean result from an unmeasured one. - GuideAssert
Security is not a CVE list
What a repository-level security read adds on top of dependency alerts: secrets, injection guards, crypto posture and the daily watch that catches what appears between commits. - GuideAssertCode Assurance Index
Gate your Backstage scorecards on the CAI
Wire Assert's verdict endpoint into Backstage Soundcheck, Cortex or OpsLevel: a per-repo key, one gate-shaped JSON read covering CAI, lenses, dimensions and rubric provenance. - GuideAssert
From finding to fix, by hand or by agent
How to hand an Assert finding to whoever fixes it, a colleague or a coding agent over MCP, with enough context that they never have to re-derive it. - GuideAssert
From code host to your first baseline
Connect GitHub, GitLab, Bitbucket or Azure DevOps read-only, add a repository, and read your first baseline CAI: what each step grants, what the first report contains, and what to look at first. - GuideAssert
Architecture drawn from the code
How Assert derives a C4 architecture map from the code itself: one diagram for the whole product, current on every survey, even when the services are written in different languages.
Documentation
14- DocumentationCCA/where-the-code-runs/
Where the code runs
The container, what we do to a repository, what leaves our machines. - DocumentationCCA/what-a-survey-is/
What a survey is
What goes in, what comes out, what repeats under the same inputs, and the three reasons a score can legitimately move. - DocumentationAssay/what-a-decision-report-is/
What a decision report is
What a buyer asks, what comes back, and what it is allowed to say. - DocumentationCCA/the-rubric-contract/
The rubric contract
Why scores stay comparable over time, how a rubric version is created and enforced, and exactly what recomputing a score does and does not establish. - DocumentationCCA/the-journey-of-a-survey/
The journey of a survey
From "survey this" to a finished report: the six stages, in order, and what happens when one of them cannot complete. - DocumentationAssay/the-journey-of-a-report/
The journey of a report
From “assess this” to a finished verdict: the stages, in order. - DocumentationAssay/the-evidence-contract/
The evidence contract
Signatures, reproduced verdicts, and why a report can be audited years later. - DocumentationAssay/quality-bars-and-acceptance-profiles/
Quality bars and acceptance profiles
The producer declares which kind of code is measured; the buyer defines what passing means. Both declarations travel with the evidence, and every deviation is disclosed. - DocumentationAssert/products-portfolios-and-deliveries/
Products, portfolios and deliveries
How a measurement becomes a statement about a thing that is bought, sold or owned: the curated product, the portfolio roll-up, the contract that obliges an attestation, and the signed delivery. - DocumentationCCA/how-we-validate-ourselves/
How we validate ourselves
How we measure our own error rate, and the two gates before a language counts as validated. - DocumentationCCA/how-we-measure/
How we measure
Lenses, dimensions, and the difference between "clean" and "we could not tell", which is the distinction most code-quality scores collapse. - DocumentationAssert/how-assert-works/
How Assert works
Start here: what this documentation covers, at what altitude, and the recommended reading route through it. - DocumentationAssay/how-a-bar-decides/
How a bar decides
Bars, versions and bindings: writing down what “good enough” means. - DocumentationAssay/customers-and-engagements/
Customers and engagements
Who the buyer is, and the live relationship through which a standard reaches a product.
Nothing of this kind for that product yet.