Skip to content
Build n Bloom
Menu
WorkflowsRolesSystem BlueprintResourcesEvidenceExisting-client NDISInstallation
Request a Fit Call
← All workflow paths

C4 · DEL.6 → KNW.1–KNW.3 · Example design

Keep the method, respect the rights

Turn permitted lessons from completed work into a reviewed, current method—or record why reuse is forbidden.

Request a Workflow Fit Call ↗How a Blueprint is scoped
TRIGGER → ACCEPTED OUTPUTCompleted case → safe reusable method

Typical sponsor: Practice and knowledge owners. This is an illustrative route. It is not an installed workflow or a promise that this path is one of your three Blueprint designs.

01 / HANDOFF DESIGN

The object, the owner, the decision.

Select any stage to inspect what it receives and produces, which specialist role might assist, what it may access, and who makes the human decision.

C4 · DEL.6 → KNW.1–KNW.3REFERENCE DESIGN · NOT AN INSTALLED SYSTEM

Scroll the diagram horizontally, or use the stage buttons below.

Completed case → safe reusable methodFive stages linked by named handoff objects. A rejected decision returns from stage 5 to stage 2. The full sequence and ownership are written below.Rights-check requestApproved reuse basisReviewable method versionVersion and permission metadataReuse rights revoked01 · DEL.6Case closesEngagement lead02 · KNW.1Reuse decisionRights owner03 · KNW.1Curated assetKnowledge owner04 · KNW.3Current methodMethod owner05 · KNW.2Permitted reusePractitioner
SELECTED HANDOFF / 01

Case closes

Engagement lead owns this step.

Receives
Accepted case and obligations
Produces
Close pack
Possible agent roles
Case coordinator
Permission boundary
Case-specific close and retention terms
Human decision
Lead confirms closure
Other stop and return routes
  • A source correction, expiry or retirement goes to the method owner (KNW.3) for quarantine or update, affected-use review and a recorded new version or retirement decision.
  • No cross-client reuse occurs until the new case's rights and relevance are checked by its practitioner.
Read the full handoff and exception sequence
  1. Case closes (DEL.6) — Engagement lead receives accepted case and obligations and produces close pack. The handoff is rights-check request. Lead confirms closure.
  2. Reuse decision (KNW.1) — Rights owner receives agreement and source provenance and produces allowed, limited or no reuse. The handoff is approved reuse basis. Rights owner decides.
  3. Curated asset (KNW.1) — Knowledge owner receives permitted content and limits and produces redacted draft asset. The handoff is reviewable method version. Method owner approves meaning.
  4. Current method (KNW.3) — Method owner receives approved version and expiry and produces published or retired method. The handoff is version and permission metadata. Owner approves publication/retirement.
  5. Permitted reuse (KNW.2) — Practitioner receives current method and new case rights and produces cited relevant source or rejection. This is the recorded outcome. Practitioner verifies fit.

Return path: Reuse rights revoked sends work from Permitted reuse to Reuse decision.

A source correction, expiry or retirement goes to the method owner (KNW.3) for quarantine or update, affected-use review and a recorded new version or retirement decision.

No cross-client reuse occurs until the new case's rights and relevance are checked by its practitioner.

02 / WHY ASSESS IT

Value is a hypothesis until measured.

Future preparation may become easier when current sources are findable; a larger library alone is not measured value.

MEASUREMENT BASIS

Records to inspect

Close pack, client rights, redaction decision, method approval, version register and future-use review.

STOP / RETURN

Where it can fail

No reuse right stops capture. Correction, expiry, withdrawal or deletion quarantines the asset and rechecks affected uses.

DESIGN ACCEPTANCE

Cases to test

Test permitted/non-permitted reuse, partial redaction, supersession, deletion and cross-client denial.

03 / SPECIALIST ROLES

Possible assistance, bounded by authority.

These roles are candidate responsibilities in the reference architecture. They are not prebuilt products or active agents in your systems.

COORD

Case coordinator

Show the next owner, dependency or proposed follow-up.

Boundary: One current case state; routine effects require separate delegation and receipt.

CURATOR

Knowledge curator

Propose safe reuse, redaction, version and retirement.

Boundary: Rights-known case material and knowledge register; no automatic cross-client reuse.

CHECK

Quality checker

Compare a draft with the original permitted evidence and exact request.

Boundary: Read-only comparison; a discrepancy report is never professional sign-off.

TECH

Technical investigator

Diagnose a defined integration, index or service interruption.

Boundary: Authorised logs and test environment; no self-approved rollback or release.

LIBRARIAN

Evidence librarian

Find current permissioned internal sources for one case and question.

Boundary: Case-scoped internal search; no public-web egress or cross-client corpus.

All ten roles ↗

From reference to a firm-specific decision

A Blueprint starts with a service the firm already sells, examines permitted records and measures the constrained work. It selects three connected boundaries, designs each to the same depth and ranks the first installation. A reference path may change, narrow or be rejected when the evidence is different.

Inspect the System Blueprint ↗