Risk LabStrong architectural inferencev1.22.1

In plain English

This page provides local browser worksheets. They help plan reviews; they are not formal safety certifications.

  • Why this matters: AI risk can come from the whole arrangement, not one obvious model.
  • What to look for: data, memory, routes, adapters, tools, evaluators, updates, and rollback paths.
  • Technical version below: the expert terminology remains available and is linked through the glossary.

Apex review playbook

Evidence levelStrong architectural inferenceTechnical label: Architectural inference

The report expansion adds a structured review path for teams using the browser-side Risk Lab tools. This page is not a certification method; it is a planning sequence.

Review sequence

  1. Use Composition Explosion Calculator to estimate the state space.
  2. Use Proposed Cognivirus terminology for the loss of confidence in an evaluation result as system components, routes, permissions, models, prompts, memory, tools, or environments change. Open glossary definition Worksheet to identify what changed since evaluation.
  3. Use Behavioral Persistence Explorer to inspect memory, descendants, synthetic data, routers, and A system that judges whether an AI output or candidate is acceptable. Open glossary definition reservoirs.
  4. Use Restoring not only a model artifact but the relevant router, prompts, memory state, tool permissions, evaluator version, deployment alias, and data dependencies. Open glossary definition Planner to inventory Returning a system to an earlier known state. Open glossary definition dependencies.
  5. Use Evaluator Independence Checklist to check whether selection pressure is trustworthy.
  6. Use The inability to identify one accountable component, developer, operator, or decision point after a distributed system produces harm. Open glossary definition Mapper to identify missing accountable owners.
  7. Use Multi-LoRA A proposed Cognivirus review category for systems where adapter reproduction, dynamic composition, persistent memory, adaptive routing, evaluator selection, and incomplete rollback reinforce one another. Open glossary definition to decide whether ordinary component review is inadequate.

Apex review triggers

Run the playbook when any of these are true:

Output

The output should be a decision record with one of four outcomes:

OutcomeMeaning
The decision not to change the system. Open glossary definitiondo not change the ecology
quarantineisolate component or route for deeper review
limited canarydeploy with traffic, memory, and tool limits
promoterelease only with signed composition and rollback records

Reminder

The worksheets do not calculate real-world probability. They identify missing evidence, stale Confidence, backed by evidence, that a system meets safety or governance requirements. Open glossary definition, and unexamined transition paths.