Incorrect diagnosis
A reproducible report reveals a wrong or ambiguous result that could make an AI choose the wrong instruction.
PUBLIC ROADMAP · UPDATED WITH PROJECT EVIDENCE
A roadmap
you can audit.
AIHostCheck does not count intentions as progress. Every milestone needs visible acceptance evidence in code, tests, documentation, an issue, or a release.
Read the source roadmapCURRENT RELEASEv0.1.0Working early foundation
VALIDATION STAGEEarlyReal-device coverage is next
COMPLETION RULEPublic evidenceCode · tests · docs · release
HOW PRIORITIES MOVE
Coverage gap
Real hardware or permissions expose evidence that hosted CI cannot validate safely.
Bounded evidence
A contribution adds cross-OS value through a documented, read-only source with a clear privacy boundary.
RELEASE TRAJECTORY
From foundation to reusable compatibility layer.
Sequence matters: first prove the evidence on real hosts, then improve distribution, then expand integrations.
00
SHIPPED
A trustworthy foundation
The first release proves the core contract: bounded local collection, explicit uncertainty, and native output an AI consumer can parse.
COMPLETION EVIDENCE
- Native Windows, macOS, and Linux CLI
- Versioned JSON contract and human-readable output
- Six release archives with SHA-256 checksums
- Cross-OS CI, privacy, security, and AI workflow guides
01
NEXT
Reliability on real machines
Move beyond hosted runners with a privacy-safe validation matrix and turn every confirmed mismatch into a regression test.
COMPLETION EVIDENCE
- Redacted fixture format for real-device reports
- Representative OS and architecture coverage
- Documented limitations for blocked or unavailable evidence
- Compatibility and provenance rules covered by tests
02
FOLLOWING
Safer distribution and AI workflows
Make reports easier to verify, inspect, redact, and reuse without requiring an account or uploading host data.
COMPLETION EVIDENCE
- Maintainable artifact-signing policy before signed releases
- Low-friction installation paths evaluated per OS family
- Local report review and redaction assistance
- Agent adapters with explicit unknown and failure behavior
03
EVIDENCE REQUIRED
Specialized diagnostic packs
Deeper GPU, accelerator, local-AI runtime, editor, and support-bundle work enters the release plan only after real workflow evidence exists.
COMPLETION EVIDENCE
- NVIDIA driver and toolkit compatibility evidence
- Additional accelerator and local-runtime ecosystems
- Capability profiles for Python, containers, and GPU work
- Plugin model only if the core stays small and auditable
SUPPORT → OUTPUT
Resources must leave public evidence.
Infrastructure support accelerates validation and delivery. It is never presented as adoption, a customer relationship, or an endorsement.
Support areaProject usePublic evidence
Cross-platform computeBroader OS and architecture validationFixtures, tests, and a public coverage matrix
Secure deliverySigning policy and verifiable native artifactsDocumented process and signed releases
Hosting & observabilityReliable docs and faster production diagnosisPublic fixes and deployment history
AI developer toolingValidate adapters across agent workflowsOpen examples and compatibility notes
NON-NEGOTIABLE BOUNDARIES
Growth without changing the trust model.
- No remote command execution
- No telemetry or background monitoring
- No automatic report upload
- No account or hosted report database
- No silent software installation or reconfiguration
- No “absent” claim when evidence is unavailable
ROADMAPS EARN TRUST THROUGH EXECUTION