How we build

Rules we build by.

These are the operating rules behind every Hidden Canopy surface. They are engineering constraints, not marketing language. When a product has to choose between them, the rule wins.

Operating rules

Eight rules, held under pressure.

Each rule is stated the way it is enforced: as a boundary, not a preference.

01

Software should serve the person running it.

Not the vendor, not the platform, and not the model. This is the first line of the Open Canopy Contract and the last line of every design review.

02

Fail closed.

When a request, a signature, or a state cannot be verified, the system denies it. It never degrades silently and never falls back to trust.

03

Receipts are evidence, not testimony.

What a component claims happened is timeline content. What its receipt proves happened is evidence. The two are never blurred.

04

Capability is not authority.

Successful training is not promotion. Confidence is not permission. A model earns limited authority and loses it the moment the evidence changes.

05

Local-first is a constraint, not a gap.

Your machine, your data, your jurisdiction. The internet is an option, not a requirement, and there is no silent cloud fallback.

06

Many minds deliberate. One voice speaks.

Plural judgment converges before any fluent answer is rendered. Smoothness is a rendering quality, not proof that a legitimate decision occurred.

07

The checkpoint may change. The claimant does not.

Identity, memory, and doctrine persist across replaced computational bodies. Promotion is hard; demotion is easy.

08

A marked gap beats a confident claim.

Simulated, cached, and unproven states are labeled as such, visibly. A system that cannot say ‘not yet’ cannot be trusted when it says ‘yes.’

Evidence discipline

Demonstrated, and not yet.

We publish both columns and keep them separate. A receipt is not a claim of funding, deployment, or acceptance — and an unfinished result is marked as a gap, not promoted into a headline.

Demonstrated

What the public record shows.

A small judgment family operating as a live routing layer upstream of a larger generative model.
Judgment separated from language generation, with a replaceable generative head.
Native C++ and CUDA training outside the conventional Python training loop, including low-precision paths.
Mechanisms that stay inactive until they have earned deployment.
Not yet

What remains open.

The complete family architecture outperforming strong conventional baselines.
Claimant identity surviving many generations of model bodies.
Net computational savings from predictive supersampling.
Generalization of the architecture across unrelated organizations and domains.
A living ledger. This list is revised as evidence changes. A source receipt, a public repository, or a working local build is never presented as award status, hosted access, or universal capability.
The Open Canopy Contract

Thirteen public commitments govern every public repository: permissionless use, no expiry, data on your machine, no surveillance pricing, the right to leave, documented formats, buildable source, legitimate forks, competition on value rather than captivity, and openness even when it becomes inconvenient.