Skip to content

trust-release: browser-local evidence readiness intake - #315

Merged
thecelestialmismatch merged 2 commits into
mainfrom
trust-release/evidence-intake-permanent
Aug 20, 2026
Merged

trust-release: browser-local evidence readiness intake#315
thecelestialmismatch merged 2 commits into
mainfrom
trust-release/evidence-intake-permanent

Conversation

@thecelestialmismatch

Copy link
Copy Markdown
Owner

Release summary

This release hardens HoundShield’s public trust boundary and introduces the Evidence Readiness Path plus a permanent Evidence Intake product page at /evidence-intake.

Included changes

  • Limits the public /api/health response to a non-secret liveness signal and introduces a fail-closed, administrator-gated diagnostics route.
  • Pins the repository, CI, application, and proxy workflow to Node 22.22.2; the proxy test configuration now avoids its native-module parallel-worker crash.
  • Adds a scoped homepage Evidence Readiness Path and removes pseudo-live presentation from the hero preview.
  • Adds browser-local PDF evidence intake with file validation, SHA-256 hashing, local text extraction, deterministic field suggestions, human accept/reject review, and local manifest export.
  • Adds the Evidence Intake surface to the authenticated dashboard and ships a permanent public /evidence-intake page with the existing shared header and footer.
  • Qualifies public metadata, product, assessment, status, and call-to-action claims to avoid unsupported certification, authorization, or automatic-compliance assertions.

Privacy and decision boundary

The Evidence Intake flow has no document upload, cloud OCR, external-model call, or automatic compliance determination. PDF analysis, review state, and manifest generation are browser-local; a human review gate is required before a record can be accepted.

Validation completed

Check Result
Application test suite 216 files, 3,006 tests passed
Application TypeScript check Passed
Application production build Passed under Node 22.22.2
Proxy test suite 92 tests passed
Proxy lint and build Passed
Staged whitespace check Passed
Release scope check 32 code-only files; no social, audit, research, temporary-preview, or sensitive-bank-document paths

Review focus

Please review the public copy and local-only privacy boundary. The production deployment should be verified on https://www.houndshield.com/evidence-intake after merge.

Harden public liveness visibility, protect administrator diagnostics, and pin the Node runtime used by application, proxy, and CI validation.

Add the scoped Evidence Readiness Path and a browser-only PDF Evidence Intake workflow with human review, local manifests, dashboard access, permanent public product page, shared navigation, and truthful privacy copy.

Qualify public claims and add regression coverage for liveness, local-only evidence handling, product-page disclosure, and dashboard privacy boundaries.
@vercel

vercel Bot commented Aug 20, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
compliance-firewall-agent Ready Ready Preview Aug 20, 2026 11:51am

@supabase

supabase Bot commented Aug 20, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project qifynzuyrdxmxlumpsrq because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

Replace C3PAO-ready, assessor-acceptance, absolute-compliance, and equivalent public copy with scoped human-review and deployment-boundary language across public pages, shared navigation, SEO metadata, reports, customer messaging, and product knowledge.

Add a public-source regression guard so prohibited readiness and hosted-FedRAMP assertions cannot return unnoticed.
@thecelestialmismatch
thecelestialmismatch merged commit 242fb19 into main Aug 20, 2026
12 checks passed
@thecelestialmismatch
thecelestialmismatch deleted the trust-release/evidence-intake-permanent branch August 20, 2026 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant