What this probe helps you decide
Whether a repo, project surface, or dependency is ready for your next move — or what specifically blocks it. Unlike the Free First Probe (which routes you to the right service), a Paid Trial Diagnostic delivers a governed findings package with evidence-backed observations, named gaps, and a concrete next step.
Best lifecycle moment
After a Free First Probe routes you here, or when you already know your question and need a governed answer — not just a fit check.
What you submit
One scoped repo or project surface, the decision you are trying to make, public evidence or safe high-level context, and any boundary notes (what to avoid, what is out of scope, what is sensitive). Do not submit secrets, credentials, or private source code through intake.
What product or surface this targets
Tell us the product, service, feature, SDK, app, workflow, dependency choice, AI-generated slice, or legacy module inside the repo/project that the probe should focus on. The repo is evidence; it is not automatically the whole target.
What we inspect
Scoped visible evidence against the accepted question: repo structure, documentation, test/CI signals, dependency state, gap/risk patterns, boundary constraints, and the buyer decision. Evidence is checked through governed inspection — not just pattern-matched.
What you receive
A governed diagnostic package with five parts:
- Verdict — a clear answer to the submitted question (ready, not ready, conditional)
- Supported findings — evidence-backed observations, each tied to what was actually seen
- Evidence gaps — what could not be confirmed from the approved surface
- Boundary of claim — what was and was not checked, and why
- Next stabilizing move — one concrete recommended action
How this differs from Free First Probe
A Free First Probe tells you which probe fits. A Paid Trial Diagnostic tells you what the probe found. The free version routes; the paid version reviews evidence, names findings, and delivers a report you can act on.
Stability Ledger
A Paid Trial Diagnostic can append deeper evidence to the private Stability Ledger for the scoped product or surface after review. The entry records what was checked, what was supported, what evidence was missing, what seams remained open, and the next closure move. Accepted probes can start or append to a private Stability Ledger; form submission alone does not automatically create one. See a public-safe diagnostic ledger entry sample.
Sample reports
See delivered diagnostic samples: Flask structure alignment (structure/docs/tests check), Flask diagnostic ledger entry, and Memory Palace claim-evidence (benchmark claim verification). Each report sample shows the full report shape: verdict, findings, gaps, boundary, next move.
After delivery
Reports are delivered as owner-review-pending. You review the findings privately before any content is shared. After review you may: accept and act on recommendations, request clarification on specific findings, optionally approve a public testimonial, or request a small Closure Verification follow-up after acting on the recommended next closure move. Closure Verification checks whether that specific seam improved, closed, regressed, or still needs rerun; it does not guarantee stability. FoldEngine does not publish findings without explicit client approval.
What this does not include
- Full code review or implementation work
- Security audit or penetration testing
- Compliance certification or legal opinion
- Guaranteed outcome or permanent stability claim
- Unbounded private-repo access
Boundary of claim
A Paid Trial Diagnostic is a bounded report tied to the accepted scope and evidence. It does not authorize unbounded private review, automatic remediation, or ongoing monitoring. If the question requires deeper or recurring coverage, the report will recommend a specific next probe or Custom / Quote engagement.
Best-fit examples
- A public repo with a concrete decision question and enough visible evidence.
- An AI-generated project that passed a Free First Probe fit check.
- A team deciding whether to stop, repair, migrate, or scope custom work.
- A dependency choice where the trade-offs need reviewed interpretation.