Proposed pilot readiness
A controlled release candidate with honest acceptance gates
Proposed Pilot Release Candidate 4 records the proposed pilot scope. The named council or organisation must confirm permission before its name is used publicly. The final reviewed commit will be frozen and tagged after the acceptance findings are resolved. A complete build is not the same as council approval.
- Version
- wexford-pilot-1.0.0-rc4
- Candidate prepared
- 10 September 2026
- Directory records
- 283
- Monitored official sources
- 354
Included in the release candidate
- Anonymous public support journeys for households, housing, businesses, farming, new arrivals and the Traveller community
- Source-linked support directory with dated review information and application-window warnings
- Indicative welfare and household calculators with calculation coverage and rule-version history
- Saved plans, watched-support opening and closing alerts, and device-to-device transfer without a public account
- Invitation-only organisation access, aggregate dashboards, staff roles, audit history and controlled local-content approval
- Guarded source-bound AI with safety tests, usage limits and a launch switch
- Automated source monitoring and operational failure alerts
- Installable low-bandwidth experience with selected public pages available offline
Required before a live council pilot
- Professional policy and calculation verification
- Wexford service-owner approval of local records
- Qualified-speaker review of translated journeys
- Independent accessibility, security, privacy and GDPR reviews
- Controlled testing with council staff and residents
- Named council owner, support process and signed pilot acceptance
Pilot change control
Critical security fixes and verified support changes may still be released. New features stay outside this candidate unless a named pilot owner accepts the change. Every accepted change must retain a source, effective date, reviewer and release record.