Why was the file-receipt offer withdrawn?
Inspect the retained technical contract and the explicit commercial withdrawal boundary. No new standalone orders are accepted.
Withdrawal record Synthetic evaluation packDocumentation · Releases + evaluation evidence
Operate from exact releases, evaluate from exact evidence.
Install the three public utilities from verified first-party archives, evaluate three current paid local tools, and inspect two withdrawn product records from strict schemas, synthetic records, rule semantics, and explicit boundaries.
Start by decision
Adopt one boundary before composing a workflow.
How did the table-shape contract work?
Inspect retained exact-byte, structural-agreement, and drift evidence without treating the record as a current offer.
Withdrawal record Synthetic evaluation packIs the claim reviewable?
Draft in the browser or validate an exact v1 evidence card locally.
Evidence Preflight setupAre the declared inputs ready?
Check authorities, exact identities, discovery counts, and byte bounds before another system executes.
Replay Input Preflight Synthetic evaluation packDid the real attempt begin?
Run one bounded preflight before one configured execution command.
Attempt Boundary setupMay this artifact advance?
Evaluate exact subject and evidence hashes against one declared lifecycle policy.
Artifact Admission setupWhich fields entered before targets?
Inspect the strict values-free schema, declared role boundaries, ordered manifest, and exclusion ledger.
Feature Freezer guide Check v1 fit Offline evaluation packCould this join know that row?
Evaluate event, availability, period, grid, duplication, revision, freshness, and candidate clock-interpretation semantics before licensing the local tool.
Temporal Auditor guide Offline evaluation packWhat exact version arrives, and what happens later?
Inspect the delivery trigger, archive contents, checksum verification, support and replacement windows, retention duty, and future-version exclusions.
Paid delivery guide01 / Evidence & review
Evidence Preflight v1.3.2
Draft a seven-record evidence card or reject a structurally incomplete, malformed, oversized, or contract-divergent card before downstream review.
Install
Add the exact first-party package.
npm install https://kaldenframelabs.com/downloads/kaldenframe-labs-evidence-preflight-1.3.2.tgzPackage SHA-2565ACA17B2FFB4EA80656194BB3874E1768592AADEF46EC69C990C08502F0A1C66
First run
Validate one exported card.
npx evidence-preflight ./card.jsonA valid card exits 0. Invalid JSON, an oversized file, changed schema constants, unknown properties, missing or short records, and invalid timestamps exit 1 without printing the card contents.
Contract
Seven records, one exact v1 shape.
- Claim
- Scope
- Provenance
- Comparison
- Failure criteria
- Known limitations
- Decision use
02 / Execution & retry governance
Attempt Boundary v0.1.0
Run one bounded preflight before one real command and retain whether execution was invoked, whether the attempt was conservatively consumed, and what protected paths changed.
Install
Add the exact first-party package.
npm install https://kaldenframelabs.com/downloads/kaldenframe-labs-attempt-boundary-0.1.0.tgzPackage SHA-256756C2C244BDC91425C723235583AAA3E5178CC01ADEC41F4DEB3872F48FFB8E0
First run
Run a reviewed plan, then verify its receipt.
npx attempt-boundary run ./attempt-plan.json --root ./workspace
npx attempt-boundary verify ./workspace/receipts/attempt-001.json0Execution succeeded, or receipt verification succeeded.
2Invalid invocation, plan, path, or receipt.
4Preflight stopped execution; the attempt is unconsumed.
5Execution was invoked but failed, timed out, or exceeded output limits.
Operator requirements
Review executable configuration before running it.
- CommandsArrays are launched with
shell: false; shell operators are not interpreted unless the plan launches a shell. - PathsControlled paths are portable relative paths contained beneath the chosen root.
- SecretsNever place credentials in command arguments; operating-system tools may expose process arguments.
03 / Repository & release governance
Artifact Admission v0.1.1
Evaluate one exact subject, required evidence, terminal markers, and one matching lifecycle receipt against a declared local policy.
Install
Add the exact first-party package.
npm install https://kaldenframelabs.com/downloads/kaldenframe-labs-artifact-admission-0.1.1.tgzPackage SHA-256FCC76ED7E897DAFD17FEA19AB81FFDE60D7C017DE976A68CD9FD0C6EB2E7FD1D
First run
Evaluate a policy against a workspace.
npx artifact-admission verify --policy ./policy.json --root ./workspace --output ./workspace/decisions/release.json0ADMIT.
1Policy denial.
2Invalid invocation or unexpected runtime failure.
Operational assumptions
Protect the policy and stabilize the evaluation boundary.
- WorkspaceRun against a quiescent or immutable workspace; the gate does not lock concurrent files.
- ClockReceipt freshness depends on a trustworthy synchronized local clock.
- ConfigurationTreat policy and allowed verifier identities as trusted configuration.
Release integrity
Verify the downloaded bytes before installing them.
Get-FileHash .\package.tgz -Algorithm SHA256sha256sum ./package.tgzCompare the result with the value shown in this documentation or the product's checksum manifest. A matching hash identifies the published bytes; it is not a signature, provenance attestation, vulnerability report, or guarantee of safety.
Machine reference
Discover the catalog without scraping the page.
The versioned JSON catalog contains the exact current releases, hashes, decisions, inputs, outputs, resources, and boundaries. Its schema is intentionally strict and both files are readable cross-origin.
Evaluating before operating?
Browse every public proof path in one place.
The Evidence Library separates synthetic paid-offer evaluation from complete free-utility packages and source, with exact hashes and explicit non-claims.