Filiolae-equivalence profile

Make the missing control
a question that can be answered.

Public silence is not proof that a frontier lab lacks an internal promotion control. A concrete profile lets labs, auditors, customers, insurers, and regulators ask what is actually enforced.

01

Exact transition identity

Are source and candidate weights content-addressed? Does authorization name the exact object the loader consumes? Can bytes change between approval and load?

02

Evaluator and evidence custody

Are code, suites, configuration, source, and candidate committed together? Can the learner see held-out material or mint the terminal result?

03

Precommitment and freshness

Are thresholds fixed before evaluation? Are stale, replayed, incomplete, malformed, unknown-key, or conflicting results denied?

04

Load-boundary enforcement

Is the Gate mandatory in the loader's control flow? Does denial guarantee no load? Can the governed process clear its own freeze?

05

Durable semantics

Are authorization intent, denial, load success, load failure, and missing outcome distinct? Can a hostile verifier reconstruct the decision?

06

Separation and non-equivocation

Who administers evaluator credentials, policy, artifacts, record, and halt authority? Can different auditors receive inconsistent histories undetected?

07

Evidence strength

Which claims are local tests, bounded acceptance, independent reproduction, or production evidence? Are failures and gaps retained?

A child follows a sequence of illuminated steps across water toward a globe
A common path for comparisonEquivalence belongs in enforceable properties, not category labels.
A human and a digital figure travel together toward the horizon

Three successful outcomes

The control matters more than ownership of the implementation.

AdoptionOrganizations deploy and independently validate Filiolae.
DisclosureLabs establish an equivalent internal control with evidence.
AdvancementSomeone publishes a stronger independently verifiable alternative.

No certification shortcut

A question set is not a trust mark.

This draft profile does not certify Filiolae or anyone else. Equivalence requires inspectable evidence, adversarial testing, administration analysis, and explicit residual risk.

AGPL obligations apply to Filiolae-derived software under their terms. They do not compel disclosure of independently developed systems or every internal evaluation.

Read the sourced landscape note