Compiler-resolved evidence

Requirements and tests

Each statement comes from its component contract. Links name the annotated methods. Missing links stay visible.

Trace gap

sola.cell:R1.1

When asked for health, cell shall report availability without owner data.

Implementation

Test

Trace gap

sola.cell:R2.1

When an owner requests the manifest, cell shall identify itself as a zero cell with no business modules.

Implementation

Test

Both links declared

sola.documentation:R1.1

When a visitor requests the homepage without credentials, documentation shall serve the generated homepage.

Implementation

Test

Both links declared

sola.documentation:R1.2

When a visitor requests a published document without credentials, documentation shall serve its content and declared media type.

Implementation

Test

Both links declared

sola.documentation:R2.1

If a requested path escapes the publication root or names an unpublished file, documentation shall return not found.

Implementation

Test

Both links declared

sola.documentation:R3.1

When a visitor requests the manifest, documentation shall identify its build and distinguish annotation links from test and proof evidence.

Implementation

Test

Trace gap

sola.history:R1.1

When an iteration is accepted, history shall expose an event identifying its actor and request.

Implementation

Test

Trace gap

sola.history:R1.2

When an owner requests history, history shall exclude other owners' events.

Implementation

Test

Both links declared

sola.identity:R5.1

Unless an unexpired grant is supplied, identity shall refuse owner data access; neither factor credential shall act as a grant.

Implementation

Test

Both links declared

sola.identity:R5.2

When the configured owner key is presented, identity shall issue a short-lived challenge and a private redemption secret.

Implementation

Test

Both links declared

sola.identity:R5.3

While an unexpired challenge is pending, identity shall refuse another pending challenge for that owner.

Implementation

Test

Both links declared

sola.identity:R6.1

Only after the configured factor approves a challenge shall identity exchange its private redemption secret for one grant.

Implementation

Test

Both links declared

sola.identity:R6.2

If approval is denied, identity shall refuse redemption.

Implementation

Test

Both links declared

sola.identity:R6.3

If the challenge expires, identity shall refuse proof and redemption.

Implementation

Test

Both links declared

sola.identity:R6.4

If the proof names another owner, was already used, or targets a decided challenge, identity shall reject it.

Implementation

Test

Both links declared

sola.identity:R6.5

When redemptions race, identity shall issue at most one grant.

Implementation

Test

Both links declared

sola.identity:R7.1

Identity shall persist only grant/redemption hashes, expire grants, and revoke a grant on logout.

Implementation

Test

Trace gap

sola.iteration:R1.1

When a nonblank prompt is submitted, iteration shall durably queue it with an identifier and creation time.

Implementation

Test

Trace gap

sola.iteration:R1.2

If the prompt or execution options are invalid, then iteration shall reject the request before creating a record.

Implementation

Test

Trace gap

sola.iteration:R1.3

Unless execution is requested, iteration shall leave the request queued without invoking a runner.

Implementation

Test

Trace gap

sola.iteration:R1.4

If source changes or archives are supplied, then iteration shall refuse them before creating a record.

Implementation

Test

Trace gap

sola.iteration:R1.5

When a submission repeats an idempotency key and payload, iteration shall return the original request; a changed payload shall conflict.

Implementation

Test

Trace gap

sola.iteration:R2.1

When an owner lists iterations, iteration shall return only that owner's requests.

Implementation

Test

Trace gap

sola.iteration:R3.1

If no runner is configured, then iteration shall refuse execution without consuming the queued request.

Implementation

Test

Trace gap

sola.iteration:R3.2

When execution succeeds, iteration shall record completion without claiming deployment.

Implementation

Test

Trace gap

sola.iteration:R3.3

If execution fails or exceeds its time limit, then iteration shall record `failed` or `timed-out` respectively.

Implementation

Test

Trace gap

sola.iteration:R3.4

If the request is unknown, belongs to another owner or has already started, then iteration shall refuse execution.

Implementation

Test

Trace gap

sola.iteration:R3.5

Where flight recording is enabled, iteration shall record the run's identifier, duration and outcome without the prompt or credentials.

Implementation

Test

Trace gap

sola.iteration:R3.6

When cancellation is accepted, iteration shall stop its process group and retain cancellation despite a racing completion.

Implementation

Test

Trace gap

sola.iteration:R3.7

After a process restart, iteration shall stop identified orphan runners, mark running requests interrupted, and preserve queued execution intent without replaying interrupted work.

Implementation

Test

Trace gap

sola.iteration:R3.8

Only after the configured verifier returns a matching receipt and patch hash shall iteration report completion and expose that patch to its owner.

Implementation

Test