KaldenFrame offers seven separately bounded ways to make one decision more inspectable. This page starts with the buyer problem; the Products storefront starts with the offer. Neither path turns the portfolio into a bundle, required sequence, or combined assurance claim.
Separate neighboring questions before comparing product names or prices.
02 / EvidenceInspect what supports the claim
Use public schemas, synthetic packs, source, releases, and explicit non-claims.
03 / EconomicsChoose the delivery model
Distinguish complete free utilities, private licensed tools, and tailored human review.
Buyer guides
Three problem families. Seven decisions that stay separate.
01 / Input shape and replay readiness
Did the table drift—and is the whole declared replay set ready?
The current paid route checks replay readiness against declared authorities, expected inputs, exact identities, discovery rules, and byte ceilings. The former standalone table-shape product remains available only as a withdrawn technical and commercial record.
Replay Input Preflight 1.0.0 · $99: stop a replay when declared authorities or required local inputs are missing, changed, outside bounded discovery rules, or over byte ceilings.
Tabular Shape Receipt · withdrawn: inspect the retained exact/shape/drift evidence, but do not treat it as an orderable offer.
What could the data know—and which fields were allowed to enter?
Availability-time leakage and target-influenced feature selection are different failure modes. One concerns when context became knowable; the other concerns whether outcome knowledge influenced candidate eligibility.
Temporal Boundary Auditor 1.1.0 · $499: audit declared event, availability, period, revision, freshness, and caller-declared clock-interpretation boundaries in local records.
Target-Blind Feature Freezer 1.0.0 · $249: freeze an ordered values-free candidate-feature contract before target values are read.
Did the attempt begin, may these bytes advance, and does the release claim fit the record?
Documentation completeness, command invocation, exact local artifact admission, and repository-specific diagnosis are four different questions. A green workflow does not answer all four.
Three complete MIT utilities · $0: Evidence Preflight, Attempt Boundary, and Artifact Admission each retain one narrow local record.
Release Boundary Review · $450: map evidence, attempt, identity, admission, and decision gaps across one named path in one public GitHub repository.
I want to inspect the public record before choosing.
Open the Evidence Library for synthetic paid-tool packs, the fictional review sample, and complete public utility evidence.
Same discipline, different economics
Free adoption, lightweight software, specialized software, and tailored diagnosis are different purchases.
The three MIT utilities are complete narrow tools. The $99 replay-input gate packages a standalone local job for individuals and small teams. The $249 and $499 tools cover more specialized local controls. The fixed review applies human analysis to one accepted public repository.
Price does not expand any offer into universal assurance. Scope, evidence, delivery, terms, and stopping boundaries remain controlled by each product record and any accepted written order.
01
Complete MIT utilities$0 · public source · narrow local decisions
02
Lightweight software$99 · standalone local check
03
Specialized software$249–$499 · deeper local controls
04
Fixed-scope human review$450 · one public repository · one named release path
Portfolio boundary
A route is not a recommendation or an assurance result.
These paths organize current public facts. They do not analyze your material, determine fitness, prove a claim, validate operator declarations, establish customer outcomes, or make one offer's record valid input for another. Identity, signatures, provenance, complete lineage, trusted time, vulnerability analysis, compliance, safety, correctness, and fitness require separate evidence and controls.
Already know the decision?
Search seven offers—or answer four closed questions.
Both paths run in the browser. Search text and finder answers are not submitted to KaldenFrame, persisted on the site, or placed in the URL by global Search; the finder uses only enumerated URL state.