Monk Loom

Security, limits, and failure behavior

Fail-closed inputs

Portable hard limits

ResourceLimit
Features and outputs1..256 each
Layers1..32
Absolute feature, weight, bias, threshold, scale, and runtime value32767
ParametersEmbedded budget, hard maximum 1,000,000
Learning rate0..1,000,000 parts per million

Direct-training limits

ResourceHard maximum
Records10,000, further reduced by the manifest
Epochs64
Adaptation steps100,000, further reduced by the manifest
One record1 MiB
One evidence file8 MiB
Total loaded corpus64 MiB

Schema version 1 accepts only root-image-owned corpus files. Every path is an explicit canonical path in the manifest or record; no recursive discovery occurs.

These limits keep integer products inside the cross-runtime exactness envelope and make model cost reviewable before inference.

Non-authority contract

The canonical attachment repeats five immutable statements: advisory only; cannot grant VFS authority; cannot override integrity; cannot cross ownership boundaries; cannot rewrite Monk policy. They are validated as data so the artifact describes its own boundary.

Threat-model boundary

The runtime proves deterministic structure and binding. It does not prove that a feature extractor is unbiased, a target is correct, a verifier is trusted, or supporting evidence is authentic. Those are host governance responsibilities. Treat output as evidence, never as an authorization token.