The foundations
- Public content contracts
- Backend validation and health checks
- Separated service permissions
- Container and migration scaffolding
B01 · B02 · B04 · B05 · B06
Implemented foundations, not deployed clinical tools.
We’re building an independent urology encyclopedia where evidence, uncertainty, AI authorship, and human review stay visible.
THE BUILD, IN PLAIN VIEW
What is implemented, what is being worked on, and what still needs to happen. Local tests are not a live clinical release.
B01 · B02 · B04 · B05 · B06
Implemented foundations, not deployed clinical tools.
B06-A · UI-001
Security work remains a separate local checkpoint.
No generated clinical articles, live reviewer console, or clinical question-answering service.
The initial corpus is planned as claimed Codex / Claude Code sessions using the owner’s existing allowances. The owner chooses a batch cap and credit reserve; drafts remain private until release gates pass. API-driven updates come later.
THE PLANNED TAXONOMY
Eighteen domains are mapped. These navigation cards do not represent completed or actively generating articles.
CORPUS STATUS
The taxonomy is broad. The corpus is not—yet.
ARTICLE BLUEPRINTS
These are interface records, not published medical articles. They contain no clinical claims.
Stones & endourology
Planned evidence-linked article shell for evaluation, management scenarios, uncertainty, and source provenance.
Stones & endourology
Planned procedure record with indications, harms, alternatives, and versioned evidence profiles.
Prostate oncology
Planned condition record separating evidence summaries from formal guideline positions.
Prostate oncology
Planned diagnostic-test record with population, reference standard, and applicability fields.
BPH & lower urinary tract symptoms
Planned presentation record organized around scope, differential pathways, and evidence cutoffs.
BPH & lower urinary tract symptoms
Planned comparison preserving each issuer’s own recommendation language and grading system.
Urothelial oncology
Planned presentation record with explicit population, jurisdiction, and uncertainty boundaries.
Kidney oncology
Planned condition record with claim-level citations, harms, controversies, and revision history.
PUBLIC CHANGE LEDGER
UrologAI identity, a visible build roadmap, searchable blueprints, and honest zero-content coverage. This is a nonclinical interface release.
UI-001Contract validation, separated service roles, a non-root container, and startup/route denial checks are implemented and tested. These are not live clinical services.
B04–B06Claimed work units and versioned build records coordinate collaborators. Initial corpus work is planned in user-budgeted, resumable batches; generation has not started.
GOV-001Versioned schemas and compatibility fixtures establish the shape of future releases. A valid schema is not clinical validation.
B02Search, browse, coverage, and disclosure surfaces established. No clinical claims published.
preview.1The interface now treats who wrote text and who clinically reviewed it as independent facts.
method.1Eighteen urology domains are visible, including the areas that have not started.
taxonomy.1THE PLANNED PUBLICATION METHOD
Planned: material claims linked to versioned sources, scope, and evidence cutoffs.
Planned: article-level checks for citations, numbers, provenance, and known failure modes.
Planned: authorship and human review recorded separately for each published version.
Planned: evidence packets and qualified specialist adjudication for substantive challenges.
This encyclopedia is an AI pilot under construction. Future published versions will distinguish AI authorship from clinical review. Automated checks cannot guarantee accuracy, completeness, or currency.
Specialist adjudication is planned but is not operational in this prototype. Verify consequential information against cited sources and current professional guidance. UrologAI is not a guideline, diagnosis tool, or substitute for clinical judgment.