Start
How it works
The lifecycle from advisory text to an evidence-backed verdict.
Every check follows the same lifecycle.
- 1Advisory text: pick a supported advisory or paste your own
- 2SERV Reasoning compiles it into a typed checklist
- 3Quote check: every item must quote the advisory word for word, or it is rejected
- 4Deterministic engine reads each app’s files and observes each condition
- 5Verdict per app, with file-and-line evidence and unknowns
- 6SERV Reasoning writes a client note from that verdict only
Who decides what
- SERV Reasoning decides what the advisory says: affected version ranges, conditions, and conditions that cannot be checked from files.
- Pich’s engine decides what the app contains and which verdict follows. It is ordinary TypeScript with fixed rules.
- A person decides what to do about “Needs manual review” and anything listed as not checkable.
Technical detail lives under Architecture.