Perceptifx project status

Interactive prototype — scripted demonstrations using simulated/replay data.

Open the interactive prototype · status.json · status.txt

Release

Release
0.1.2 · Public review build of prototype v0.1.1
Deployed (build time)
2026-11-07T15:44:42.618Z
Source commit
091c2e186e816d3bc32b72565d0a1b96f61a96c4
Repository
https://github.com/edgarbirlew-source/perceptifx (pending: repository not created yet; the commit shown here is held locally and will be pushed unchanged)
Hosting
Railway project perceptifx, service perceptifx-web (Bun function serving these static files; no database, no write endpoint). Deployment 11e0b7b1-beb9-435f-ae4f-50777f8a980b. Domain registration and DNS: Vercel, team ConstrucFi.
Last status update
2026-11-07T16:05:00Z by Claude (deployment thread)
How status changes
Official status changes only through a commit to data/status.json in the source repository, followed by a redeploy. The website has no write endpoint.

Progress

Progress counts acceptance items that have evidence. Research, prototype and production are counted separately. Demo progress inside the prototype is not project progress.

Research 3/21 items met

Viability3/4 (75%)

Summary, live-state record and competency skeleton saved; waiting for Edgar's read (review, not a gate).

Technical research0/6 (0%)

Items T1–T6 defined, none accepted.

Market research0/3 (0%)

Items M1–M3 defined, none accepted.

Legal / access research0/4 (0%)

Items L1–L4 defined, none accepted.

Benchmarks0/4 (0%)

Items B1–B4 defined, none accepted.

Prototype 7/8 items met

Interactive prototype7/8 (88%)

7 of 8 items have author-run test evidence (50/50 automated checks against the same build, served by the same Railway function code, on a local server). P8 is partly verified: outside browsers load the public site (Railway request log: HTTP 200 for /, 308 for www), but the full automated suite has not yet been run against https://perceptifx.com. Independent reproduction and Edgar's review are open.

Production no items defined

Production build—

Not started — gated on research and owner approval per feature.

What works today

What is scripted, simulated, replayed or live

ElementKindNote
Production observations, interpretations and next actionsREPLAYPredetermined fixture text. No website is contacted.
Login-page detectionSCRIPTEDStep 3 always fails by design; no real file parsing.
SHA-256 valuesPROTOTYPEReally computed in the browser, but only over fixture byte strings.
"Sample County" document detailsSIMULATEDFictional jurisdiction and file.
QC views and gap measurementsSIMULATEDDrawn from fixture parameters; not captured images, real ModelForge renders, or measured geometry.
QC judgmentSCRIPTEDA fixed rule function. Deterministic, not a model.
Lesson proposals L-001 and L-002SCRIPTEDPredetermined text, triggered only by the MF-001 correction.
Lesson evaluation, activation gate, rollback, historyPROTOTYPEReal logic running over the scripted rules. It shows the lifecycle, not that a model learns or generalizes.
Your corrections and demo actionsPROTOTYPEStored verbatim in your browser only. Never sent anywhere.
Anything live or autonomousNONENo live automation, no live model, no third-party site access in this release.

Prototype acceptance items with evidence

IDItemResultEvidence
P1Operator console with Workspace, Production, QC, Learning, Evidence and plain-English statusMETAutomated tests W1–W3 (all views open from a fresh browser) · results
P2Agent shows observation, interpretation and next action; reviewer can pause, correct, take overMETAutomated tests T10a–T10d, W4 · results
P3Replay of a document-acquisition run with a login page saved as "PDF" and the verifier catching itMETAutomated tests T10a–T10d · results
P4QC case: first view "no defect", agent requests more views, then confirmed or insufficient-evidence statesMETAutomated tests T1–T1c, T6b–T6d, T7, T8 · results
P5Correction captured, scoped lesson proposed, tested on held-out and counterexample, activate or reject, rollbackMETAutomated tests T2a–T9e · results
P6Persistence across reloads and a reset controlMETAutomated tests T11a–T12b · results
P7Every element labeled; nothing presented as liveMETAutomated tests L1–L2 (release label visible in every view) · results
P8Verified access instructions: the link opens and can be operatedPARTIALRailway request log shows outside browsers receiving HTTP 200 from https://perceptifx.com and 308 from www; certificate valid per Railway. Full automated run against the public URL pending (the test environment's network policy blocks the host). · results

Known defects

None recorded.

Known limitations

Active work, blockers and next action

WorkResponsibleBlockerNext action
Source repository on GitHubClaude (deployment thread); Edgar creates the empty repositoryThis agent session is not permitted to create GitHub repositories. The source and its commit history are ready to push.Edgar creates an empty private repository edgarbirlew-source/perceptifx; Claude pushes the existing commits and connects Vercel to it.
Run the automated test suite against https://perceptifx.comClaude (deployment thread)The test environment's network policy does not allow perceptifx.com.Allow perceptifx.com in the cloud environment's network settings, or have another agent run tests/public-site.test.js against the public URL.
Independent reproduction of the prototype testsUnassigned (ChatGPT/Kathy or Tom/Perplexity)NoneOpen https://perceptifx.com, follow the steps under What works today, and compare with the test results.
Technical research T1–T6Claude coordinating; Perplexity capacity to be confirmedNone recordedStart T1 primary-source review of computer-use reliability and cost per task.
Next action: Push the source to GitHub as soon as the repository exists, then begin technical research item T1.

Owner gates

GateDecisionState
G1Repository and hosting for the prototypeApproved by Edgar on 2026-11-07 for this prototype release (hosting on the existing Vercel team, no new paid plan).
G2Point perceptifx.com at a hostApproved by Edgar on 2026-11-07 for this prototype release.
G3Any spend (hardware, hosted browsers, paid APIs)Not approved.
G4Live automation against third-party websitesNot approved.
G5Expanding autonomy beyond supervisedNot approved.
G6Outbound messages or commitmentsAlways owner-sent.