July 21 Final Freeze and Submission Report¶
Late qualification and video update¶
The qualified candidate is now 0.1.0-alpha.3 at merge commit
8c059a05d1c7d0d472dd074b762678cc35fb705f, tagged
guardian-node-build-week-2026-qualified. The release workflow built and
checksum-verified both versioned Windows installers. A Windows 11 all-in-one
installation passed setup, service, ACL, dashboard, synthetic flow, and rendered
UI qualification. A separate Windows 11 child node paired with an isolated
staging backend and proved real agent capture, encrypted upload, heartbeat,
local OCR, deterministic detection, and alert persistence.
The mild synthetic gaming alert was then reviewed through the live server-side
OpenAI Responses API. The request asked for gpt-5.6, returned
gpt-5.6-sol, completed in 36,481 ms, validated schema 1.1.0, and persisted
the structured result and local parent feedback. No real family data was used.
The temporary API key was removed from staging immediately afterward and the
service was restored to mock mode. This proves the live path without asserting
that store:false is an account-wide zero-retention guarantee.
The final video asset is 168.000 seconds at 1280x720 with H.264 video, AAC
OpenAI Coral narration, and embedded English captions. SHA-256:
649e01da5944f193a8801d09dfed3001d0526ddd14fc8d53c8db49ca420b55de.
The narration explicitly explains what the owner built, how Codex with GPT-5.6
was used during development, and how GPT-5.6 is used at runtime. YouTube upload,
public/signed-out verification, /feedback, and Devpost submission remain
account actions.
Repository outcome¶
GuardianNode is frozen at version 0.1.0-alpha.2 for the Build Week candidate.
The final release identity is guardian-node-build-week-2026-final; the immutable
release commit is
62590db1911cb84cf01b27de76ab26f238d003d7. The baseline remains
pre-build-week-2026 at
36b2a547056d40eff32f00aa59b7820f7d3e98d5.
The repository package includes final README and Devpost copy, release notes, configuration/setup/demo/troubleshooting guides, synthetic screenshots, an explicit prior-work disclosure, evaluation results, and a complete Codex computer video kit with timed shot manifest, voiceover, captions, operating prompt, disposable mock server, and final watch-through checklist.
Final local verification¶
Environment: Linux 7.0.12 x86_64, Python 3.12.13, Node 24.18.0, npm 11.16.0. This is source/release automation evidence, not clean Windows-node evidence. A failed, unavailable, or manual gate remains visible.
| Gate | Result | Notes |
|---|---|---|
| Backend + synthetic E2E | 276 passed, 0 failed, 0 skipped in 58.34 s | Linux source environment; one documented Starlette/httpx deprecation warning |
| Windows-agent unit suite | 59 passed, 0 failed, 0 skipped in 9.45 s | Does not replace real-node qualification |
| Dashboard unit/type/build | 19 passed; typecheck/build passed | Embedded production bundle exactly matched |
| Release/control suite | 62 passed, 0 failed, 0 skipped in 6.06 s | Includes submission/video helper checks |
| Unique automated total | 416 passed | Backend/E2E + agent + dashboard + release/control |
| Mock browser golden path | Passed; 5 functional frames in 17.29 s | Disposable synthetic data only; incident → preview → consent → assessment → feedback |
| Mock CLI golden path | Passed | Synthetic concerning result, schema 1.1.0, encrypted local persistence |
| 55-case mock evaluation | 55 completed, 0 failed; 55/55 schema compliant | 45.45% category agreement and 0% false-alarm rate disclosed |
| Authorization/security regression | Passed | Included in backend suite |
| Secret scan | Passed | Exact candidate scan and all 130 reachable commits were clean |
| Dependency audits | Passed | No known backend/agent vulnerabilities; dashboard reported 0 production vulnerabilities |
| Lint/type/compile | Passed | Backend/agent Ruff, backend mypy across 81 files, Python compile |
| Rules benchmark | Passed | 196 frozen cases, no gate failures, p95 0.116 ms |
| Docs/governance/submission | Passed | Strict MkDocs, notices, controls, version, feature matrix, local links, required copy/video assets |
| Public link checks | 5/5 HTTP 200 | Repository, baseline tag, comparison, docs site, license; unauthenticated requests |
| README install commands | Backend dry-run and Linux shell syntax passed | Windows-only agent extra cannot resolve pywin32 on Linux; verify tomorrow on Windows |
| Windows installer workflow | Passed | Final release workflow; artifact generation only, not real-node qualification |
The first candidate tag, guardian-node-build-week-2026, exposed a release-CI
unit-test dependency on host Tesseract before any installer artifact was
published. It remains immutable. The readiness test was isolated from that host
dependency, while dedicated OCR readiness tests remain in place; the corrected
merge is tagged separately with the final identity above.
Frozen release artifacts¶
The final GitHub workflow built a draft prerelease from the immutable final tag. The draft is deliberately not public before tomorrow's clean-node qualification. The downloaded checksum file verified both Windows artifacts:
| Artifact | Bytes | SHA-256 |
|---|---|---|
GuardianNodeChildSetup-0.1.0-alpha.2.exe |
56,820,658 | a487937abc44e80036a5eb0d823868e7fdb3d06c60efe8724a873758c008251d |
GuardianNodeServerSetup-0.1.0-alpha.2.exe |
36,198,946 | b289432a8a97c7ad93dab13e09984f83925b12c6b8716a977dd40c7ab3a8fd15 |
The generated manifest records tag guardian-node-build-week-2026-final,
commit 62590db1911cb84cf01b27de76ab26f238d003d7, and build time
2026-07-19T17:45:51.9192364Z. The workflow also produced SHA256SUMS and
release-manifest.json alongside the installers. Code signing remains an
explicit manual release gate.
Live GPT-5.6 mode was not run in this environment: no server-side API key was present and the operator had not confirmed approved ZDR controls. The service correctly remains disabled rather than weakening those gates.
Codex session and submission state¶
/feedback must be run by the maintainer in this same Codex project thread.
The Session ID has not been invented or committed. Store it only in the private
notes template. YouTube upload, signed-out video verification, Devpost form
submission, and confirmation capture are external account actions and remain
unchecked until performed.
Readiness decision¶
Repository and submission-material readiness is complete for everything that
can be verified without a real node or external account action. Overall final
submission readiness is 88/100: the source, evidence, mock demo, video
production kit, final tag, and draft artifacts are ready; the clean Windows
qualification, live synthetic GPT-5.6 check, public video, /feedback, and
Devpost submission remain. Beta hardware readiness remains conditional on
tomorrow's clean Windows-node test.
No document treats mock mode as GPT-5.6 output, store:false as a zero-retention
guarantee, Guardian Review as truth/diagnosis, or the pre-existing platform as
Build Week work.