# The algo records whose meta is true

This index as JSON: https://banes-lab.com/json/api/facets/algo/meta/true

## Entries

- [<Agent Generation Concern>](https://banes-lab.com/records/algo/agent-generation-concern.md): <Load context> → <Detect capabilities> → <Check collisions> → <Discover domain evidence> → <Build knowledge> → <Analyze risk> → <Design phases> → <Compose portable contract> → <Render adapters> → <Validate grounding> → <Audit> → <Report>
- [<Workflow Orchestration Concern>](https://banes-lab.com/records/algo/workflow-orchestration-concern.md): <Load orchestration grammar> → <Discover workspace config> → <Select shared documents> → <Define agents> → <Classify parallel vs sequential> → <Fork discovery contexts> → <Serialize action phases> → <Build 4D graphs> → <Create handoff protocol> → <Coordinate shared-document refinement> → <Integrate checklist and capabilities> → <Validate template>
- [<Architecture Anti-Pattern>](https://banes-lab.com/records/algo/architecture-anti-pattern.md): <Local shortcut> → <Missing control> → <Repeated usage> → <Implicit dependency> → <Boundary/contract erosion> → <Systemic fragility> → <Expensive remediation>
- [Architectural Relationship Algebra](https://banes-lab.com/records/algo/architectural-relationship-algebra.md): <Parse concept records> → <Build relationship graph> → <Classify design force> → <Select applicable concepts> → <Resolve prerequisites> → <Detect violations> → <Measure evidence> → <Choose refactors> → <Enforce gates> → <Govern evolution>
- [Structural Core](https://banes-lab.com/records/algo/structural-core.md): The architectural rules that preserve structural integrity — a single authoritative source, no shortcuts, no fallbacks, no duplication, no orphaned artifacts.
- [Correctness Core](https://banes-lab.com/records/algo/correctness-core.md): The rules ensuring behavioral correctness and validity — no silent failures, no hidden invalidity, feedback acted on, results observed.
- [Evolution Principles](https://banes-lab.com/records/algo/evolution-principles.md): The rules governing how a system changes over time — no backward-compat cruft, no deprecation debt, no legacy retention, no 'for now'.
- [Resource Core](https://banes-lab.com/records/algo/resource-core.md): The rules governing resource lifecycle and ownership — bounded lifetime, single ownership, no leaks, no implicit retention.
- [Execution Core](https://banes-lab.com/records/algo/execution-core.md): The rules governing execution flow — a single observable path, no deferring, no dual-path branching, nothing unobserved.
- [Computation Core](https://banes-lab.com/records/algo/computation-core.md): The rules governing computation determinism and purity — no mutable shared state, no hidden nondeterminism, reproducible results.
- [Security Core](https://banes-lab.com/records/algo/security-core.md): The rules governing security posture — no hardcoded secrets, validated input, least privilege, no insecure fallbacks.
- [Performance Core](https://banes-lab.com/records/algo/performance-core.md): The rules governing performance discipline — measured optimization, planned capacity, no guesswork.
- [Contracts Core](https://banes-lab.com/records/algo/contracts-core.md): The rules governing interfaces and contracts — explicit typed boundaries, versioned change, no implicit or breaking contracts.
- [Causality Core](https://banes-lab.com/records/algo/causality-core.md): The rules governing causal ordering and time — logical ordering, retractable state, no wall-clock dependence.
- [Declarative Core](https://banes-lab.com/records/algo/declarative-core.md): The rules favoring declarative over imperative — declared configuration, separated concerns, no imperative wiring.
- [Extensibility Core](https://banes-lab.com/records/algo/extensibility-core.md): The rules governing extension — declarative discovered wiring over hardcoded, no imperative hardcoded registration.
- [Observability](https://banes-lab.com/records/algo/observability.md): The rules ensuring a system is observable — emitted metrics and signals, no unobserved execution, no opaque runtime.
- [Enforcement Core](https://banes-lab.com/records/algo/enforcement-core.md): The rules ensuring discipline is enforced programmatically — automated gates over convention, no discipline-only reliance.
- [Atomic Boundary](https://banes-lab.com/records/algo/atomic-boundary.md): The rules governing atomicity — a transactional boundary that fully commits or fully rolls back, no partial commit, no deferring within.
- [Human Factors](https://banes-lab.com/records/algo/human-factors.md): The rules governing human ergonomics — bounded cognitive complexity, acted-on feedback, explicit approval, no unlimited options.
- [Domain Modeling](https://banes-lab.com/records/algo/domain-modeling.md): The rules governing domain boundaries — bounded contexts, ubiquitous language, no leaky context.
- [Design Patterns Core](https://banes-lab.com/records/algo/design-patterns-core.md): The rules governing design-pattern use — patterns applied only to demonstrated recurrence, no speculative pattern application.
- [Architectural Contract Algebra](https://banes-lab.com/records/algo/architectural-contract-algebra.md): <Classify architectural force> → <Declare boundary> → <Define contract> → <Choose pattern> → <Bind implementation> → <Verify invariant> → <Observe runtime> → <Govern evolution>
- [<Automation Concern>](https://banes-lab.com/records/algo/automation-concern.md): <Detect static coordination point> → <Classify intentional vs problematic> → <Measure scale pressure> → <Verify convention strength> → <Design dynamic contract> → <Preserve fallback> → <Validate performance and architecture> → <Capture knowledge>
- [<Centralization Concern>](https://banes-lab.com/records/algo/centralization-concern.md): <Detect context> → <Classify pattern> → <Discover all occurrences and variants> → <Choose canonical source> → <Map migration> → <Gate execution> → <Validate zero debt> → <Report evidence>
- [Cross-Stage Invariants](https://banes-lab.com/records/algo/cross-stage-invariants.md): Bind every stage to the always-and-never rules of the generator — resolve authority and directionality before planning, discover before assuming, activate principles with a bound validator, order by dependency with severity as routing metadata, read only the prior stage's output contract through one evidence-bearing handoff, represent all four graph axes, require evidence for every claim, separate generation gates from future execution gates, repair from the earliest invalid stage, and render deterministically.
- [<Checklist Governance Concern>](https://banes-lab.com/records/algo/checklist-governance-concern.md): <Orient on authority + evidence> → <Plan principles + protocols + dependency graph> → <Compile atomic tasks + ripple chains> → <Validate reasoning by evidence + semantic policy> → <Repair from the earliest invalid stage> → <Render one bounded terminal>
- [<Compliance Verification Concern>](https://banes-lab.com/records/algo/compliance-verification-concern.md): <Load rules> → <Run authoritative verifier> → <Parse failures> → <Classify by violation type> → <Apply bounded fixes> → <Run local post-fix validation> → <Rerun verifier> → <Exit on pass or bound>
- [<Context Verification Concern>](https://banes-lab.com/records/algo/context-verification-concern.md): <Detect required contract> → <Bind allowed capability> → <Execute bounded operation> → <Validate evidence> → <Emit typed result>
- [CSS Type-Cascade Kernel](https://banes-lab.com/records/algo/css-type-cascade-concern.md): Declare one layer order, hold every value in tokens, key every appearance on a type — native or custom-registered — exactly once in globals, hold placement in components and assembly in app, create all DOM through a factory that stamps types and refuses inline style, and gate the whole contract behind machine fitness functions.
- [<Governed Plan Concern>](https://banes-lab.com/records/algo/governed-plan-concern.md): <Seed the phase> → <Investigate and execute under gates> → <Self-inform from canon and self-audit> → <Capture and reconcile considerations at the boundary> → <Close only on a mechanically resolved gated state> → <Re-seed the next phase>
- [<Living Accumulation Concern>](https://banes-lab.com/records/algo/living-accumulation-concern.md): <Compose prior memory as disclosed evidence> → <Capture only same-turn verified deltas> → <Merge idempotently by stable identity, bounded> → <Version and log only real change> → <Persist against the connection fork> → <Overlay onto the immutable baseline>
- [<Mode-Driven Response Schema>](https://banes-lab.com/records/algo/mode-driven-response-schema.md): Make the model's structured output a mode-driven composed contract — the output mirror of composed input context: per loop-owned mode the schema and instruction are projected from one field registry, the response is validated and self-heals against it, the typed fields are governed, and every turn is persisted as a versioned queryable record — so the output has one source, cannot drift from its instruction, and can be audited.
- [<PAG Instruction Concern>](https://banes-lab.com/records/algo/pag-instruction-concern.md): <Declare document type and jurisdiction> → <Draw grounded uppercase directives> → <Decompose into headed, contracted, gated nodes> → <Bind semantic operations and structure declarations> → <Bound with invariant records> → <Validate well-formedness against the failure taxonomy>
- [<Pattern Distillation Concern>](https://banes-lab.com/records/algo/pattern-distillation-concern.md): <Initialize evidence workspace> → <Measure current architecture> → <Group semantic families> → <Extract behavioral signatures> → <Detect duplicate/inconsistent behavior> → <Score anti-patterns> → <Evaluate abstraction boundary> → <Compose reusable schematic> → <Migrate with rollback> → <Verify old-pattern elimination> → <Record ROI>
- [Quality-Engine Kernel](https://banes-lab.com/records/algo/quality-engine-concern.md): Resolve a canonical policy into a per-ecosystem CheckPlan, order its stages by the invalidates relation, normalize the proposal, run generation checks on the server and project tools via the relay, derive a machine verdict, and drive a bounded downstream cascade to clean — holding no runtime execution in the engine itself.
- [<Taxonomy Concern>](https://banes-lab.com/records/algo/taxonomy-concern.md): <Resolve jurisdiction from the declared roots> → <Order containers by reshape risk> → <Walk each path into ordered roles> → <Classify each file to its narrowest concern> → <Project the name and its folder chain together> → <Reshape one container at a time> → <Hold every proposed word at the admission gate> → <Verify pattern-resolved discovery survived> → <Ledger the state> → <Terminate on no residual finding>
- [<Test Coverage Concern>](https://banes-lab.com/records/algo/test-coverage-concern.md): <Load the surface catalog for a unit> → <Walk the dimension x lens grid> → <Derive the required-uncovered surfaces> → <Prioritise by risk> → <Select a mode-matched technique and its invariant> → <Author the test> → <Issue an evidence verdict> → <Ledger the coverage state> → <Terminate when no required surface is unknown>