Compatibility: Pactmark 0.1.x. API names remain English in every locale, including the
Turkish documentation. Only prose is translated.
Core objects
Compiled agent contract
Instructions, schemas, tools, model profiles, policy and verifiers, reduced to a versioned identity
with digests.
Authorised bounded work
Tenant, principal, purpose, input, budgets, deadline and the exact accepted definition. A
WorkOrderRequest is what a caller sends; an AcceptedWorkOrder is what the system stores.Event-derived execution
Not an object you mutate. A run is its ordered event history;
RunProjection is a derived cache.Content-addressed output
Identified by the digest of its exact bytes.
A check over exact bytes
Returns a versioned
VerificationResult bound to an artifact digest, a verifier registration and a
rubric version.A bounded, redacted claim
Carries
supports and doesNotProve, both required and both non-empty.Authority
Who is acting, and in which tenant
Passed as the first argument to every runtime method. There is no ambient current user.
Permission with an expiry
Binds tenant, principal, purpose, tool registration, scope, expiry and constraints.
A consumed one-use decision
Bound to tenant, run, effect, policy, grant, scope and expiry — never free-form text.
A one-use, expiring proof
Issued after authenticating the actor; consumed atomically into a decision.
Opaque credential references
Short-lived and purpose-bound. Resolved only inside the bound adapter.
Effects
A change outside the run
Recorded through
prepared → dispatched → acknowledged, or into uncertain and
needs_reconciliation.Stable operation key
What makes an idempotent retry meaningful for a
native strategy.A separately authorised reversing run
Not an undo. A new
WorkOrder with its own authority and evidence.Modes
Status labels
Status labels distinguish locally evidenced behaviour, experimental or pilot behaviour, and future work.Words this documentation avoids
Not: “secure”
Specific controls address specific risks. Nothing here establishes that a system is secure.
Not: “compliant”
Evidence is an input to your control framework, not a regulatory conclusion.
Not: “exactly-once”
At-least-once with controlled effects, and uncertainty recorded as a state.
Not: “sandboxed”
The reference container is a test fixture. Isolation requires a separately assessed system.
Not: “verified” (unqualified)
Always: verified against what, by which verifier, under which rubric version.
Not: “production-ready”
Readiness is evaluated per profile, in your environment, and it can fail.
Language policy
The canonical public language is English, with required Turkish companion documentation. API names, error codes, event types, field names and enum values are never translated — a Turkish page describingwaiting_for_approval uses waiting_for_approval.
What Pactmark does not prove
Where the avoided words would otherwise have appeared.
Evidence
Why claim language is bounded by schema, not by style guide.