Trusted niche layer target
- 100+ public records
- 30+ agentic routes
- 1200+ near-question hooks
VAREXIS-INDEX
Daily evidence review and publication is scheduled at 09:00 Europe/London on the operator host. It requires the host and app to be available. Paid service availability is reported separately by the live capabilities endpoint.
Submit a bounded question or inspect a sample receipt. Pay first, then email your request. The owner handles it asynchronously when available; no fixed turnaround is promised.
VAREXIS-INDEX uses a daily entry-building workflow to convert existing evidence into public-safe records, question routes and paid-service routing. This is not represented as a fully autonomous public runtime bot.
122 public records; 108 agentic routes; 1528 near-question hooks. 38 VAREXIS evidence summaries, 44 external documentation references and 40 derived claim-boundary records. Documentation and derived entries are not VAREXIS experiments. Near-question hooks count distinct wording across records, routes and contexts; repeated wording is counted once.
candidate_inventory
Identify existing evidence artefacts, runs, ledgers, validations, failures, refusals or development records suitable for public-safe indexing.
boundary_classification
Classify as supported, safe refusal, not demonstrated, challenged, not qualified, development-only, protocol-only or receipt-only.
public_safe_record_draft
Create machine-readable summary record with canonical question, near questions, supported claims, not-demonstrated claims and private boundary.
agentic_question_generation
Generate near-question hooks and route them to one or more records.
service_mapping
Attach free discovery, single request, receipt, research or Developer/API route.
catalog_publish
Publish JSON record, catalog entry and context route.
build_and_verify
Run local build, commit, push, GitHub Action and live marker validation.