Toolkit 2.0.0
The current public release of the installable discovery, delivery, controls, assurance and adoption system.
The Loom Toolkit 2.0.0 · released
Install the method. Give it your institutional DNA.
The Toolkit includes the Institutional BrainKit: a private, governed seed for code, PRDs, architectures, interfaces and reports. Human owners approve it; repositories pin it; the Loom applies it where the work happens. Its present evidence comes from a synthetic reference build—not customer production use.
middleleap / ai-dlcLoom Toolkit 2.0.0
Discovery + deliveryPolicy compilerContinuous assuranceManifest-driven adoptionThe Loom Toolkit / public core
Your BrainKit / private seed+Optional domain intelligence
Executive view
The method is The Loom. The installable product is The Loom Toolkit.
AI-DLC is the technical distribution mechanism—not a competing consulting proposition. The Toolkit carries the method into the repository and binds it to institution-owned context.
Reference-build validated
Exercised end to end while building the synthetic Open Finance Backoffice reference portal.
No customer production use
It has not been used to deliver or operate a customer production system.
Your BrainKit
A private, human-approved package of institutional language, architecture, technology policy and decision rights.
AI-DLC
The repository and plugin mechanism used to distribute, version and adopt the public Toolkit.
The adoption path
Install the frame. Draft the identity. Put owners in control.
The public toolkit installs from one manifest. The first institution-owned artifact is a private BrainKit, reviewed by accountable humans and pinned into each repository that adopts it.
Capability adoption path / 05Frame → install → draft → approve → compound
Advisory
Regulatory, commercial and operating questions are resolved at leadership level.
The Loom Toolkit
One manifest installs the harnesses, controls and templates, preserves existing agent settings and reports anything that still needs a human merge.
BrainKit draft
Approved sources become draft identity, terminology, architecture, technology policy and decision rights; unknowns remain visible gaps.
Human governance
Accountable context owners approve the private release; product repositories mount a digest-pinned snapshot.
Institution
Each governed change binds the institutional profile while the wider context brain grows through delivery cycles.
Installed capability
MethodPrivate BrainKitCompiled control plansOptional domain packs
Operable by the institutionWhat you can adopt
One governed delivery system. A compiled route for every change.
The public proposition is deliberately smaller than the technical marketplace: a core toolkit whose compiler commands execution, plus domain packs when the mandate requires them.
Core bundle / Governed delivery systemLoom 2.0.0 · AI-SDLC 1.0.0
The Loom Toolkit
The customer-facing core combines The Loom's governed method, the Institutional BrainKit and repository foundations that compile each change into the gates, evidence and accountable decisions it requires.
- Discovery + delivery harnesses
- Institutional BrainKit
- Compiled control plans
- Continuous assurance
- Governance + evidence controls
- Safe, merge-aware adoption
Domain pack 01 / UAE domain intelligencev2.1
Open Finance Intelligence
The first attachable domain pack brings CBUAE and AlTareq knowledge, Islamic-banking context, risk review and value-proposition prototyping into the core system.
- Open Finance canon
- Islamic banking UAE
- UAE bank risk reviewer
- UI/UX prototyper
For builders
Install the frame. Then draft the institution's seed.
Version 2.0.0 adopts the Loom from one copy manifest, preserves an existing .claude/settings.json and writes a sidecar when human merging is required. BrainKit templates land as a draft: the generator may organise approved sources and expose gaps, but only accountable humans can approve the result.
/plugin marketplace add middleleap/ai-dlc
/plugin install middleleap-loom@middleleap-ai-dlc
/plugin install middleleap-ai-sdlc@middleleap-ai-dlc
# install the Loom inside the repository
/middleleap-loom:loom-adopt
# draft the BrainKit from approved sources
/middleleap-loom:brainkit-init
# optional domain intelligence
/plugin install middleleap-open-finance@middleleap-ai-dlcYour institutional BrainKit
One governed seed—not a second compliance database.
The BrainKit owns institutional DNA. It references regulated context and solution-domain assets without duplicating either, keeping each source of truth clear.
Regulated context
Mandates, deadlines, risk taxonomy, controls and security posture.
Solution domain
Contracts, data models, personas, scopes and evaluation assets.
Institutional DNA
Architecture, approved technology, design system, terminology, voice and approval routes.
BrainKit scopeInstitution-owned context layerVersioned once · digest-pinned per repository
Institutional signals
- Design standards
- Approved terminology
- Architecture principles
- Technology constraints
- Controls + decision rights
Institutional BrainKit
A private package of institutional identity, terminology, architecture, technology policy and decision rights.
Draft firstHuman-ownedVersionedDigest-pinned
Every Loom artifact
- PRDs + discovery artifacts
- Code + architectures + ADRs
- Interfaces + prototypes
- Reports + evidence packs
Draft from evidence
The generator uses approved institutional sources only. Unsupported decisions go into a gap register.
Approve with humans
Accountable owners review the package. The agent can seal digests, but it cannot approve institutional context.
Pin the release
Each repository mounts the private snapshot. Its institution profile and compiled plans record the BrainKit digest.
Validate in CI
Once compiled, CI checks the approved version, canonical sections, complete digest envelope, source grounding, D7 provenance and artifact provenance—and rejects undeclared BrainKit files.
From package to capability
Adopt it around one bounded outcome.
Use an AI-native delivery pilot to draft the first BrainKit from approved sources, establish accountable ownership and leave a digest-pinned, manifest-installed harness in the repository.