Public JS/TS referenceQuality gate: passWording: Kimi K2.6 · English
Next.js 16 full-stack template
A compact full-stack starter used to test whether FlowPreflight stays cautious when a repository contains framework capability but limited product-specific behavior.
Measured analysis work, not a sample-based AI opinion
These are workload and retained-evidence counts, not defect counts. FlowPreflight inventories source first, then connects the observations into routes, functions, effects, controls, and journeys.
Files inventoried
54
40 supported files parsed
Source facts connected
661
Imports, declarations, calls, routes, data operations, and other source observations
Functions analyzed
30
Static behavior analysis; not proof of runtime execution
Dependency candidates
0
Checked for advisory evidence; production reachability remains separate
Artifacts retained
73
Reports, diagrams, evidence, validation, and traceability records
WHAT WE DID
From repository to validated report
01
Pinned the public repository to an immutable commit before analysis.
02
Indexed source, routes, package scripts, imports, functions, controls, and effects without executing project code.
03
Compared the reconstructed request path with authentication, data-access, build, reliability, and release knowledge.
04
Validated the Customer Report, Technical Dossier, Prompt Pack, provenance, and cross-artifact counts.
WHAT THE RESULT ESTABLISHED
A useful review without invented certainty
Recognized the Next.js, authentication, MongoDB, and frontend-state stack.
Reconstructed the GET /post request path, including its response and scheduled timer effect.
Published ten focused follow-up checks instead of turning limited starter context into defects.
PUBLICATION CHECKS
Deterministic analysis first. Controlled AI wording second.
FlowPreflight selected the evidence, journeys, decisions, priorities, and tasks without an LLM. Kimi K2.6 received only bounded report sections plus the minimum canonical context needed to improve the English wording. It did not receive the repository, analysis databases, full dossier, or full canonical report, and it could not add or remove a finding.
Schema and reference validation
Canonical counts, IDs, and claim levels preserved
English-only output validation
Public-output and secret-safety checks
Customer Report and Prompt Pack quality gates passed
Report publishedNo confirmed release blocker was established from the available evidence. Follow-up work remains attached to the exact evidence boundaries.
Artifact quality checks passed
BEFORE YOUR NEXT DEPLOY
Get the same evidence trail for your codebase.
See the flows AI generated, the controls source evidence supports, and the exact checks that still need a human or runtime signal.