Open the exact material
Use direct first-party links, version labels, and full SHA-256 values. Avoid evaluating an offer from prose alone.
Public nowSeven current offers + two withdrawn recordsExact artifacts
Pre-purchase evidence / 01
Inspect before you decide.
Descriptions tell you what an offer is for. Evidence lets you test whether its boundaries are concrete. This library puts every current public evaluator, sample, schema, package, source archive, and checksum—plus retained evidence for two withdrawn standalone offers—in one place beside the claim each artifact cannot support.
How to read this library
An artifact supports a bounded decision.
Exercise the visible boundary
Compare clean and adversarial synthetic records, validate schemas, run public tools, or inspect the service sample.
Honor the non-claim
A sample is not a customer outcome. A checksum is not a signature. A synthetic pack is not the private implementation.
Current and withdrawn private software records
Evaluate behavior and boundaries. Not a free implementation.
These five packs are offline, synthetic, and checksum-bound: three support current paid offers and two are retained withdrawn-product records. None includes or executes the private implementation or grants a commercial software license.
Local Input Receipt
Inspect a two-file synthetic input, deterministic receipt, and an added/changed-path comparison without receiving executable receipt logic.
What you can inspect
- Offline evaluation ZIP and external SHA-256
- Strict receipt schema, original and changed synthetic inputs, expected receipt, and comparison
- Withdrawal record, historical commercial boundary, and retained technical contract
What it cannot establish
No provenance, authorship, completeness, semantics, independence, replay readiness, reproducibility, security, compliance, safety, fitness, or access to the private implementation.
Pack SHA-256
BA0F3A6CA38EE40DF0DBBCB4ADED464F6456C9662396EB849EFB7DDF6677B5C4Tabular Shape Receipt
Inspect one deterministic receipt plus exact, shape-match, and drift comparisons across three tiny synthetic tables without receiving executable receipt logic.
What you can inspect
- Offline evaluation ZIP and external SHA-256
- Receipt, verification, and comparison schemas plus exact expected JSON
- Withdrawal record, historical commercial boundary, and retained technical contract
What it cannot establish
No provenance, authorship, completeness, semantic correctness, distribution stability, absence of leakage, security, compliance, safety, fitness, executable implementation, or current availability. Column names, basename, and exact source SHA-256 are retained.
Pack SHA-256
CF7EE9AC62B9FC983B1E89EE1EF3E07EE8E135FFDB3706AE7A3DE33F73C79546Replay Input Preflight
Inspect one synthetic READY pack and one synthetic BLOCKED pack without receiving executable preflight logic.
What you can inspect
- Offline evaluation ZIP and external SHA-256
- Two strict schemas plus clean and adversarial contracts and expected packs
- Exact offer, purchase route, and commercial terms
What it cannot establish
No replay execution, semantic or independence validation, completeness proof, reproducibility, security, compliance, safety, fitness, or access to the private implementation.
Pack SHA-256
017498C8CA4E093A64C86E684748272CBA3868CAFE0FFDE49C3D8D6F14CB191BTarget-Blind Feature Freezer
Inspect how a values-free schema and explicit policy become one selected feature, five reasoned exclusions, and exact byte identities—without exposing target values or the implementation.
What you can inspect
- Offline evaluation ZIP and external SHA-256
- Clean and exclusion-focused synthetic contracts, schemas, and manifests
- Evaluator guide, fit checker, strict offer, and commercial terms
What it cannot establish
No proof that operator roles are correct, upstream computation was target-blind, hidden proxies are harmless, leakage is absent, features are useful, or the private implementation is included.
Pack SHA-256
25889EE51674894E2848DF7C43C2FBDEF353C76F4E72FB196FF35DBE6103F403Temporal Boundary Auditor
Inspect exact clean/adversarial temporal audits and dominant/ambiguous clock probes without receiving executable audit logic.
What you can inspect
- Offline evaluation ZIP and external SHA-256
- Four strict schemas plus complete synthetic inputs and deterministic outputs
- Evaluator guide, fit checker, strict offer, and commercial terms
What it cannot establish
No factual-data proof, true clock, complete lineage, causality, absence of every leakage channel, statistical validity, production safety, fitness, or access to the private implementation.
Pack SHA-256
468C8D98109B3D76991F24636B71D315A536BA83207D570E693C45761E6DFF3APaid fixed-scope review
Inspect the report shape. Keep the sample fictional.
The sample demonstrates decision mapping and reasoning density. It is not customer work, a real repository assessment, a vulnerability report, or evidence of outcomes.
06 / $450 · Fixed scope
Release Boundary Review
The Northstar Relay excerpt shows a release-decision map, three evidence-referenced boundary findings, a prioritized roadmap, an evidence register, and explicit non-findings.
- Actual paid input
- One public GitHub repository, one named release path, one decision, and non-sensitive context.
- Actual paid output
- A repository-specific written report and one timely consolidated follow-up email.
Public evaluation route
- Wholly fictional sample report
- Browser-local scope classifier
- Strict machine-readable offer
- Visible terms, privacy, security, refund, and exclusion boundaries
Cannot establish: customer adoption, a customer result, private-repository capability, implementation work, security assurance, certification, or release success.
Free MIT utilities
Inspect source and run the exact release. Boundaries still apply.
These are complete narrow public utilities, not teasers. Their value is the decision they make inspectable; their open source does not expand that decision into universal assurance.
Evidence Preflight
Check whether a technical claim is documented well enough to enter serious review.
- Package SHA-256
5ACA17B2FFB4EA80656194BB3874E1768592AADEF46EC69C990C08502F0A1C66- Source SHA-256
58B67AFF6EFE2CF7F16F2D1ED676E92D9D7DF4B496216EAA0D6366624DABB64B
Stops at: documentation completeness—not factual truth, causality, statistical validity, reproducibility, safety, or fitness.
Attempt Boundary
Distinguish preflight rejection from invocation of a real execution attempt.
- Package SHA-256
756C2C244BDC91425C723235583AAA3E5178CC01ADEC41F4DEB3872F48FFB8E0- Source SHA-256
7BAEDD2EE3D77D69DA7714B7E106B5D2CB9D1A9B17861829C92835EA28AA3F13
Stops at: observed attempt accounting—not sandboxing, command safety, non-access, host integrity, correctness, or fitness.
Artifact Admission
Decide whether one exact implementation may advance under a declared policy.
- Package SHA-256
FCC76ED7E897DAFD17FEA19AB81FFDE60D7C017DE976A68CD9FD0C6EB2E7FD1D- Source SHA-256
B35F6DA91C73FDA910FA77B2AA34DD1F8D60816FB9F5A3207452DEF44245C29F
Stops at: local consistency and policy admission—not signatures, build provenance, vulnerability scanning, evidence truth, safety, or fitness.
Common evidence boundary
Public evidence enables scrutiny. It does not manufacture outcomes.
- No customer identities, results, endorsements, adoption, demand, revenue, or production-performance claims.
- No private software implementation, wheel, commercial delivery archive, tests, reference inputs, or reconstructive edge in paid evaluation materials.
- No hash treated as a signature, authorship proof, provenance attestation, trusted timestamp, safety result, or fitness decision.
- No sample treated as a security audit, certification, compliance attestation, vulnerability assessment, or guarantee.
Evaluation FAQ
Know what the material gives you—and where it stops.
The visible and structured answers are exact. Product pages, offer contracts, licenses, and accepted written scope remain controlling.
01Do the paid evaluation packs contain the licensed software?
No. The Local Input Receipt, Tabular Shape Receipt, Replay Input Preflight, Temporal Boundary Auditor, and Target-Blind Feature Freezer packs contain public schemas, synthetic inputs and expected outputs, boundary notices, manifests, or checksums. They contain no executable implementation, wheel, commercial archive, private tests, reference inputs, customer material, or software license.
02Are the report samples or synthetic outputs customer evidence?
No. All published evaluation records are first-party synthetic material. The Release Boundary Review excerpt is wholly fictional, and the paid-tool inputs and outputs are deterministic synthetic examples. None is a customer result, endorsement, adoption signal, or performance claim.
03What can a checksum establish?
A matching SHA-256 value establishes that the compared bytes are identical. It does not establish authorship, authenticity, provenance, safety, correctness, source truth, a trusted timestamp, or fitness for a decision.
04Can I inspect and run the three free utilities before deciding?
Yes. Each free MIT utility has a direct package, source archive, public GitHub repository, versioned release, schemas, release notes, and checksum manifest. Evidence Preflight also has a live browser worksheet. Their explicit boundaries still apply.
05What should I do after reviewing the evidence?
Use the browser-local fit checker before requesting a paid tool or the review service. For a free utility, inspect its product page and documentation, verify the published bytes, and test it in a bounded non-sensitive environment before adopting it.
Next decision
Choose the offer, then inspect its boundary again.
Use the catalog for full descriptions, the finder for guided routing, pricing for commercial terms, or the workflow map for where each decision stops.