District Command product roadmap
Full office operating system
This roadmap shows what is being prepared, why Senate staff would use it, and what must be completed before it can be presented as live. Items are candidates, not promised dates.
Current foundation
Today's product already includes on-demand official records, a District 18 map, legislative and oversight workbenches, evidence receipts, and review-first Post Office drafting. Snapshot generated Sep 5, 2026, 10:26 AM CDT.
Anticipated releases
Surfaces city and county agendas, minutes, packets, notices, and decisions before they become constituent surprises.
Sealy and Austin County first, followed by reviewed official sources across all 18 District 18 counties and major cities.
Verify each official endpoint, publication cadence, document format, and partial-county match rule.
Lets staff search an entitled newspaper issue, open the exact page, and identify stories that warrant office review.
Secure manual Sealy News PDF intake with page-linked text, provenance, review state, and restricted original-file access.
Complete licensed-content rights evidence, secure upload/storage, malware checks, OCR, access control, retention, and deletion.
Moves a reviewed Post Office draft into the office workflow without retyping and without scraping recipient addresses.
Save drafts to the signed-in staff mailbox and choose recipients only from office-approved Microsoft or CRM lists.
Approve Microsoft mail scopes, mailbox audit rules, contact ownership, retention, and recipient authorization.
Shows transportation, water, permit, disaster, and capital-project records against the exact PLANS2168 boundary.
Add reviewed TxDOT project records and further agency layers with location, status, funding caveats, and source receipts.
Record source-specific distribution approval and activate each governed connection only after exact-boundary QA.
Gives four district offices one queue for intake, county routing, agency ownership, deadlines, escalations, and resolution history.
Permission-scoped cases, consent records, private attachments, duplicate detection, service levels, and staff ownership.
Approve the private-data model, consent language, tenant roles, records schedule, audit trail, and secure document handling.
Keeps hearings, testimony, agency promises, questions, recommendations, and follow-up deadlines in one evidence trail.
Committee dossiers, witness and testimony review, commitment tracking, agency deadlines, and hearing-ready staff briefs.
Connect reviewed official hearing materials and define staff ownership and records-retention rules.
Moves high-priority district changes to staff attention without requiring someone to refresh every source manually.
Staff-controlled schedules, severity thresholds, source-failure alerts, morning summaries, and acknowledged follow-up tasks.
Approve background processing, notification channels, operating ownership, quiet hours, monitoring, and cost controls.
Finds emerging local concerns while keeping official records—not social sentiment—as the source of record.
Verified public-page monitoring through approved Facebook, Instagram, YouTube, and other platform APIs with direct citations.
Verify page identities, platform permissions and terms, rate limits, deletion behavior, and political-opinion privacy boundaries.
Helps staff answer a district question across bills, hearings, local records, projects, and licensed publications with exact citations.
Permission-aware answers with page-level evidence, visible uncertainty, and a clear not-enough-evidence result.
Approve retrieval access, citation quality tests, data-class separation, model controls, and human-review requirements.
A feature moves out of this page only after its exact source, permissions, security boundary, tests, staff workflow, and deployed behavior have been verified. District Command will not label planned capability as live.