Know What Works, What Is Being Tested, and What Is Next.
This page explains how INO should publish evidence-backed software and service status for its website, membership systems, consultation module, and administrative tools.
Current public availability must be proven independently of archived ZIP files and code snapshots.
Status Classifications
Use one consistent classification across every feature.
Planned
A requirement or design exists, but no supported implementation has been accepted.
In Development
Code or page drafts exist; acceptance testing, security, or operational integration remains incomplete.
Staging / Release Candidate
A test package exists, but production deployment and complete functional acceptance remain unverified.
Verified Available
The live feature is accessible to intended users, documented, tested end to end, and owned by a support process.
A Public Release Gate
A release note should answer four concrete questions.
Which release is installed?
Record the precise production version, deployment timestamp, source revision, and dependencies.
What was tested?
Attach a reproducible test summary, role checks, security review, and compatibility results.
What can users complete?
List successful live flows, observed limitations, and confirmed forms or notifications.
What is the recovery plan?
Document backups, rollback, administrator ownership, support, and outstanding defects.
Reference Artifacts in Project Materials
The shared INO Platform package names include People Web v1.7.4-rc.1, Enrollment v1.7.5-rc.1, and Membership Lifecycle v1.7.6-rc.1. These are supplied artifacts; their filenames do not verify which release, if any, is currently active on the live site.
Chief Ballots and THE AMERICAN RECORD™ are separate proposed or candidate components. Their own approvals, dependencies, and version evidence must be recorded rather than inherited from the main platform.
Important Questions, Clear Answers
Does “release candidate” mean a feature is live?
No. RC indicates a test-ready candidate, not an accepted production deployment.
Why not publish all forms immediately?
Unverified forms may collect sensitive data without adequate authorization, storage, or notification controls. Public collection should follow verified readiness.
Institutional / Legal Scope: This is a disclosure and release-management page; no individual module is designated production-ready without separate verifiable live evidence.
Continue With an Informed Next Step.
Explore the relevant records and programs, participate through the correct channel, and help advance INO with verified information and accountable institutional practice.
This is a disclosure and release-management page; no individual module is designated production-ready without separate verifiable live evidence.