The organism · what it says when it breaks

The words I use when something fails.

All 12 sentences VEILOS can say about a failure — proven just now, live, against provider-shaped inputs carrying identifiers. A system under strain will tell you something. The question is whose words it uses — because a payment provider's error message, passed through unchanged, publishes identifiers the system would never have published on purpose.

12sentences · 2 about myself · 10 about someone else

Proven live, this request

provider_declined ← a provider naming the object it refused
provider_rejected_credentials ← a provider naming this deployment's key
provider_unreachable ← a runtime naming internal structure
provider_unavailable ← a database naming a column
provider_unreachable ← a socket naming an internal address

Each line is a real call into the real boundary, made while rendering this page, on an input carrying an identifier a visitor must never receive. The left column is everything that came back.

RELAYED

provider_unreachable

VEILOS says: the outbound call never reached the provider.

About someone else's failure — reported, never quoted. · an identical retry can succeed

RELAYED

provider_timeout

VEILOS says: the provider did not answer in time.

About someone else's failure — reported, never quoted. · an identical retry can succeed

RELAYED

provider_declined

VEILOS says: the provider refused the request as posed.

About someone else's failure — reported, never quoted. · retrying unchanged cannot succeed

RELAYED

provider_rejected_credentials

VEILOS says: the provider rejected this deployment's credential.

About someone else's failure — reported, never quoted. · retrying unchanged cannot succeed

RELAYED

provider_missing_resource

VEILOS says: the provider has no such object.

About someone else's failure — reported, never quoted. · retrying unchanged cannot succeed

RELAYED

provider_rate_limited

VEILOS says: the provider is rate-limiting this deployment.

About someone else's failure — reported, never quoted. · an identical retry can succeed

RELAYED

provider_failed

VEILOS says: the provider answered with its own failure.

About someone else's failure — reported, never quoted. · an identical retry can succeed

RELAYED

provider_response_unreadable

VEILOS says: the provider answered in a shape we could not read.

About someone else's failure — reported, never quoted. · an identical retry can succeed

RELAYED

provider_not_configured

VEILOS says: this deployment has no credential bound for that provider.

About someone else's failure — reported, never quoted. · retrying unchanged cannot succeed

RELAYED

provider_unavailable

VEILOS says: the provider lane failed in a way we did not recognise.

About someone else's failure — reported, never quoted. · an identical retry can succeed

OURS

internal_unreadable_state

VEILOS says: the durable record could not be read for this computation.

About VEILOS's own failure. · an identical retry can succeed

OURS

internal_computation_failed

VEILOS says: an internal computation threw and was contained.

About VEILOS's own failure. · an identical retry can succeed

Why bound a failure at all

Every privacy boundary before this one asked whether a value VEILOS wrote may be seen. A failure answers with words VEILOS did not write, so no projector had ever been applied to it. This census names the whole vocabulary the organism is willing to speak when something breaks, marks which sentences are about itself and which are about someone else, and re-runs the boundary live on provider-shaped inputs every time you load this page.

The provider's own sentence is not destroyed — it is retained where only the founder key can read it, correlated to a visitor's receipt by an opaque incident id. Bounding what is published is not the same as forgetting.

Machine census (JSON) → · The Boundary Census → · The Abstention Ledger →