Truthfulness rule
Request Confirmation and Reference Numbers
Saved Early Access and User Access requests now display a reference number and explain manual review, email follow-up, and invitation-based access. The number is for follow-up only, not a public status lookup or access credential.
Public impact: Applicants see what to expect after submission without exposing private review details or implying automatic approval.
Controlled Early Access Readiness
The public site now describes active Early Access testing and provides dedicated Early Access and general access-request paths. Requests are stored for manual owner/admin review; trial, Early Access, and Approved Tester access remain distinct. Stripe billing remains disabled until explicit owner confirmation.
Public impact: Outside users can request the appropriate access level, while evidence requirements, private-tool protections, and interest-only pricing remain visible.
Admin Tool Navigation Routing
The admin area now uses a real parent route for /admin with the dashboard mounted at /admin/. Admin tool pages render as sibling child routes, and the horizontal menu performs explicit client-side navigation to the intended protected tool page.
Public impact: No public product access changed. Owner/admin users can move between admin tools without the dashboard remaining mounted after the URL changes.
Authentication Flow Result Handling
The sign-in and signup flow now produces explicit outcomes instead of depending only on passive session events. Successful password sign-ins navigate directly into the private platform, email-confirmation signups route to a dedicated confirmation page, and OAuth/email confirmation redirects preserve the intended app destination.
Public impact: Founder/admin and future approved tester access is clearer: after submitting auth forms, users either enter the private app or see a specific next-step confirmation page.
RebuildReady Output Governance
RebuildReady now applies evidence-based governance to every output it produces. Package requirements — industry, application type, deployment environment, intended outcome, and available evidence — determine which analyses run, which deliverables can be completed, which remain provisional, which require human confirmation, and which cannot honestly be produced. Missing evidence is documented as an explicit gap with its operational consequence and the requirements to resolve it. RebuildReady does not generate unsupported documentation to complete a package.
Public impact: The private Legacy Code Risk Scan report now shows a RebuildReady output governance section. Public documentation at /docs/rebuildready-governance explains the rules.
Prelaunch Documentation Foundation
The initial documentation library explains access levels, early access, tester requests, private scanner guidance, report interpretation, metrics, code privacy, limitations, pricing research, admin workflows, and glossary terms.
Public impact: Visitors can now understand what Modernize Agent AI is, what is available now, what is private, and how to request access.