Creator and verifier roles
The user-directed Council is designed to design, create, repair and improve DataChips, typed Circuits, Genomes and full compatible systems, not merely select pre-existing optimization utilities. Creator proposals need independent model review, executable oracles, hardware-limit awareness, source licence checks and auditable experiment journals. A roster and a model API catalog do not prove each model has replied independently.
Reconstruction and self-repair
A full system import should produce a capability inventory and reproducible defects. NIKI may propose missing DataChips and repair source, receive precise compiler failures, regenerate only affected components, then compare outputs against immutable original examples and independent acceptance criteria. Failed hypotheses are retained in ADAM/BTDU. Promotion requires signed authorization and appropriate external testing, not assistant-invented repair success.
Current test evidence
Provider roster/credential admission regression passed 7/7 local tests. Genuine remotely hosted-model probes were not reliable: one nominated model gave no usable output, another returned HTTP 429. The Grand Forks cutblock task used one real creator and no independent reviewers. NIKI selected a public British Columbia consolidated cutblock source and retrieved real geospatial features, but the generated assembly did not compile because a required dataset socket was missing. This is positive original-data retrieval, not a complete certified drone/ecology product.
Required next independent proofs
Prove actually separate model responders and independently evaluated roles; repeat full invention-to-executable-to-repair cycle on arbitrary owner-authorized projects; execute bounded tests on genuinely separate qualified FarmNodes; establish full ENTITY owner-signed authority; and verify final products in their real intended environment. Do not describe a 25-row interface as a qualified 25-model Council or automatically generated circuits as qualified inventions.
Sources, qualification and related records
Council system guide · Cross-system status.
Figures refer to scoped local Windows engineering logs as at 25 October 2026. A passed test count does not equate to measured customer deployment. Proprietary source, keys, model credentials, sensitive identity and private account information are not published.