Produced
Content or a file was created.
EVIDENCE & LIMITATIONS
Trust starts
with distinctions.
We do not present a retrieved source as guaranteed truth, or a signature as validation of substance. Evidence should state what it covers, and what it does not.
Evaluated
Defined checks addressed specific elements.
Authorized
An operation meets the conditions for access and use.
Signed
An artifact’s integrity is verifiable through the supplied mechanism.
MATURITY INDICATORS
Separate states.
Not a blanket promise.
Summary of the development update provided on 12 September 2026. No live monitoring or new acceptance tests are performed by this illustration.
Existing workflow
A website and interface appear in the founder’s screenshots. Their presence does not demonstrate every operational assurance.
Document Workspace
Editing, references, versions and exports have been reported on the local stack. Deployment of these changes has not been announced.
Pilot environment and providers
Real-provider testing, pilot isolation and full UX validation are not established in the latest supplied update.
Spreadsheets and wider integrations
Unreleased capabilities and LAB hypotheses remain separately identified. An architecture diagram is not evidence of availability.
EVIDENCE WITH AN EXPLICIT SCOPE
One result.
Its sources.
Its limitations.
Useful evidence identifies the relevant version, data used, checks actually performed and conditions for reuse.
A signature can establish a package’s integrity and stated origin. It does not, on its own, show that every claim is accurate.
An offline verifier cannot know about a change or revocation published after its latest available information.
EXISTING PUBLIC RESOURCES
Inspect rather than
take our word for it.
Links to the current website, not checked live during this preparation. Review their data and versions before relying on them.
Existing verifier ↗
Inspect a package and the scope of its signature mechanism.
Existing Proof Graph ↗Explore the current presentation of the evidence workflow.
Existing status page ↗Read the date and nature of observations without inferring a blanket assurance.
Existing published benchmark ↗Check version, scope, unmeasured cases and methodological limits.
IMPORTANT QUESTIONS
What we
keep separate.
Does APLOMB guarantee every answer?
No. A check has a defined scope. It must disclose its sources, method, limitations and unevaluated elements. A certificate does not replace review suited to the use case.
Does governance prevent creation?
The goal is to preserve approved capabilities and separate permission to create from the level of verification. Mandatory organizational restrictions still apply.
Does “built in France” mean no data leaves France?
No. Destinations depend on hosting, model, endpoint, tools and settings. Each configuration must be examined before sensitive use.
Is APLOMB LAB a certification body?
The LAB refers to APLOMB’s applied research effort. No certification authority, official qualification or audit independence is claimed.
What is the accessibility status?
The design includes keyboard navigation, focus indicators and responsive layouts. This is not a compliance audit. The final website still needs accessibility testing.
EVALUATION RECORD / TARGET FORMAT
A number is not enough.
It needs a method.
Each published result must state what was tested and what was not. This template is not a benchmark result.
APLOMB LABTEMPLATE · NOT MEASURED
Evidence continuity
after a document edit.
- Question
- Can an edit retain a useful link without inheriting a validation that no longer applies?
- Version & scope
- To be completed for the campaign actually carried out.
- Method
- Defined cases, references, execution conditions and counterexamples.
- Results
- Not provided. No test is represented by this illustration.
- Limitations & next steps
- Errors, unexecuted cases, uncertainty, reproduction and decision.
YOUR USE CASE COMES FIRST
Let’s build your
next AI use case.
A practical case. A clear scope. Outcomes to assess together.