CORE METHOD / IO
Start a conversation Studio
FOLLOW THE EVIDENCEONE COMPANY. ONE PICTURE.

YOUR COMPANY'S OPERATIONAL DIGITAL TWIN

Make your
company work
as one intelligent
system.

We build AI assistants, internal applications and connected workflows around the systems your company already uses.

Start with one module. Expand around your work.

CASE FILE4471THE MISSING CONNECTION

INCOMING / CUSTOMER MAIL

“Where is
my order?

08 SEP · 09:47

EARLIER SNAPSHOT / 04 SEP

CRMDelivered
OPERATIONSNot shipped
FINANCEUnpaid

Three systems. Three answers.

The answer is already
in your company.
It just isn't connected.

An illustrative company case. Follow the records.

01 / DEMAND

Before an order,
there is a signal.

The first connection is between attention
and an actual business opportunity.

EXHIBIT 01 / THE MARKET

14opportunities
across 13 countries
A world view, one case in focus World geography with a close view of the European illustrative case. Aalen is the origin; Lyon, Brno and Gothenburg are three selected locations. Markers are approximate city locations. The map does not show a global customer network. {"geography": "Natural Earth, public domain", "world_projection": "Natural Earth I", "inset_projection": "Equirectangular; standard parallel 52 degrees north", "coordinates": "Approximate city centers at two decimals", "scope": "Geographic context for an illustrative European case. Aalen origin and three selected city examples. No global customer distribution is asserted.", "precision": "Approximate city coordinates, not factory or customer addresses.", "boundaries": "World view uses physical land only. Inset follows Natural Earth default de facto boundaries; no sovereign labels or territorial claims."} WORLD / GEOGRAPHIC CONTEXT EUROPE / CASE DETAIL Aalen Lyon Brno Gothenburg Approximate city locations Aalen to three selected locations. Case origin Selected examples
CRM · SELECTED CASE LOCATIONS

SEARCH CONSOLE / 91 DAYS

1,240 clicks

“parts washer retrofit”

Prior 91d121
Last 91d178
11 JUN TO 09 SEP 2026

CRM / ORIGIN OF ENQUIRIES

11Website
+
3Trade fair
=
14Opportunities
AGGREGATE CHANNEL VIEW
02 / SALES

A number in the pipeline.
A promise to someone.

SALES ORDER CONFIRMED / 18 AUG 2026
No.4471CONFIRMED
Order 4471 line items
DESCRIPTIONQTYEUR
Filtration retrofit kit235,800
On-site commissioning12,600
NET TOTAL38,400
ERP · SALES ORDER 4471

ACCOUNT MANAGER / CALL NOTES

“The line stops
in week 37.”

Both kits on site before 7 September.
Delivery 1 September agreed.
Partial delivery not wanted.

18 AUG · CRM NOTE
ENQUIRY
14 Jul
QUOTE
29 Jul
WON
18 Aug

The order total is in the ERP.
The real deadline is in a conversation.

03 / OPERATIONS

Every system is certain.
They can't all be right.

EXHIBIT A.1 / CRM

Delivered

FINAL

Set by the invoice sync.
No carrier event checked.

04 SEP / ORDER 4471

EXHIBIT A.2 / OPERATIONS

Not shipped

FINAL

Assembly slot held.
No delivery note exists.

04 SEP / ORDER 4471

EXHIBIT A.3 / FINANCE

Unpaid

FINAL

Invoice issued.
EUR 38,400 still open.

04 SEP / ORDER 4471

THE MISSING PART / FR-2210-B

One housing short.

ON HAND
1
RESERVED
2
AVAILABLE
−1

Below reorder point since 12 August.
Purchase order raised 13 days later.

04 / FINANCE

A missing part.
A misleading forecast.

EXHIBIT C / RE-26-0917

Invoice.

EUR 38,400

Issued
01 September
Trigger
Planned-delivery run
Supporting delivery note
None at issue
Payment
Still open
ERP / ACCOUNTS RECEIVABLE

THE WIDER PICTURE / 10 SEP

4.18M

EUR in open receivables.
61 invoices. Each with its own story.

A forecast is only as good
as the event behind it.

05 / THE HUMAN GATE

Intelligence knows
when to stop.

A PERSON DECIDES

Operations lead
OWNER OF RECORD

EXCEPTION E-0931 / ORDER 4471

Ship part of the order,
or wait for both kits?

A

Propose a partial shipment.Buyer consent and dates required.

B

Wait. Ship complete.Decision recorded 26 Aug, 08:30.

The 10 Sep estimate misses 1 Sep and the pre-shutdown requirement. The customer was not notified; revised-date acceptance is not recorded.

WORKFLOW / OPERATIONS LEAD
AUTHORITY, PER ACTION
  1. M0Observe
  2. M1Propose
  3. M2Wait for approval
  4. M3Run within policy
06 / THE RECEIPT

Not another answer.
An answer with evidence.

RE: WHERE IS MY ORDER?

Shipped Tuesday.
Expected Thursday.

Order 4471 was collected at 09:41.
Two pallets, 386 kg. Destination: Lyon.

08 SEP / SOURCES ATTACHEDTRACEABLE

EXHIBIT D / CARRIER SCAN

09:41

Picked up.
Aalen plant → Lyon

44 0871 2265 3

Pickup is confirmed.
Arrival and the customer handoff
still need confirmation.

07 / WHAT WE BUILD

Your company.
Connected around the work.

01 / INTEGRATE

AI Assistants & Knowledge

Knowledge assistants, customer memory and prospect research, connected to approved sources.

02 / BUILD

Workflow & Data Integration

Internal applications, CRM and ERP connections, and recurring work with clear approval rules.

03 / ASSURE

AI Security & Assurance

Access controls, security testing and action records your team can inspect.

04 / MEASURE

Measurement & Reporting

Measurement diagnostics, data reconciliation and automated reports with checkable sources.

One module. Your existing systems.
Scope it together. Test it with your team. Expand from there.

08 / YOUR DIRECTION

Orchestrate
your company.

With the whole picture.

Choose what runs, what needs approval, and when the system stops.

Your direction.
Connected execution.
Evidence you can inspect.

CASE 0001
FREE / FIXED SCOPE

System Boundary
Review.

Find the first workflow worth changing.

  1. 01 A baseline and a target
  2. 02 Authority for each action
  3. 03 An acceptance test you can rerun
  4. 04 An expand-or-stop decision

The review is free. Implementation is a separate, paid engagement.

09 / THE WHOLE PICTURE

Every connection
changes the picture.

Thread: connected context Triangle: a person decides

Explore the case file

The company and its records are illustrative. Open a document to follow the evidence behind the answer.

INTRODUCTION
Make your company work as one intelligent system.

CORE METHOD

YOUR COMPANY'S OPERATIONAL DIGITAL TWIN

Make your company work as one intelligent system.

CORE METHOD · THE CLAIM · 2026-09-10

Assistants that answer with sources.

CORE METHOD

Assistants that answer with sources.

Software that runs within policy.

Workflows that stop when they should.

CORE METHOD · WHAT WE BUILD

Where is my order?

ILLUSTRATIVE COMPANY RECORD

Where is my order?

Order 4471 · promised 1 September

Asked Tuesday 09:47 · no answer yet

CUSTOMER MAIL · 2026-09-08 09:47 · UNANSWERED

DEMAND
WORLD / EUROPEAN CASE DETAIL

ILLUSTRATIVE COMPANY RECORD

WORLD / EUROPEAN CASE DETAIL

Illustrative opportunity register: 14 opportunities across 13 countries

Origin: Aalen, Baden-Wuerttemberg

Selected locations shown: Lyon, Brno and Gothenburg

Pins represent approximate city centres, not exact customer or factory addresses

The world outline provides geographic context; it does not indicate customers or operations on other continents

Nearest Basel, about 230 km; farthest Porto, about 1,700 km, by approximate straight-line distance from Aalen

CRM · ACCOUNT ADDRESSES · PLOTTED 2026-09-10

SEARCH CONSOLE · 91 DAYS · 11 Jun to 9 Sep 2026

ILLUSTRATIVE COMPANY RECORD

SEARCH CONSOLE · 91 DAYS · 11 Jun to 9 Sep 2026

Clicks 1,240 · Impressions 58,900

CTR 2.1% · Average position 13.8

The query that grew: parts washer retrofit

178 clicks · preceding 91 days, 12 Mar to 10 Jun: 121 · +47%

4,120 impressions · CTR 4.3%

SEARCH CONSOLE · beispiel-maschinenbau.example · EXPORT 2026-09-10

COMMERCIAL OPPORTUNITIES · 14 · AS OF 2026-09-10

ILLUSTRATIVE COMPANY RECORD

COMMERCIAL OPPORTUNITIES · 14 · AS OF 2026-09-10

01 Hydraulic components · Lyon · WON (order 4471)

02 Automotive tier 2 · Brno · QUOTED

03 Pump maker · Gothenburg · QUOTED

04 Gear maker · Eindhoven · QUALIFIED

05 Aerospace machining · Bilbao · QUALIFIED

06 Medical implants · Graz · QUALIFIED

07 Bearing maker · Wroclaw · QUALIFIED

08 Valve maker · Bergamo · QUALIFIED

09 Compressor maker · Aarhus · NEW

10 Contract machining · Coventry · NEW

11 Turned parts · Basel · NEW

12 Agricultural drives · Linz · NEW

13 Tooling maker · Porto · NEW

14 Fastener maker · Leuven · LOST (price)

11 enquiries through the website form · 3 from the September fair

Channel totals are recorded separately from search clicks. Individual search-query attribution is not recorded.

CRM · PIPELINE EXPORT · 2026-09-10 · SOURCE FIELD: SITE FORM / FAIR

SALES
QUOTE Q-2611 · Lyon · hydraulic components

ILLUSTRATIVE COMPANY RECORD

QUOTE Q-2611 · Lyon · hydraulic components

Filtration retrofit, two washing lines

EUR 38,400 net · margin 31% (EUR 11,904)

Enquiry 14 Jul · sent 29 Jul · WON 18 Aug

Became order 4471

CRM · OPPORTUNITY 2611 · WON 2026-08-18

QUOTE Q-2614 · Brno · automotive tier 2

ILLUSTRATIVE COMPANY RECORD

QUOTE Q-2614 · Brno · automotive tier 2

Spare-part package and spindle overhaul

EUR 21,750 net · margin 28% (EUR 6,090)

Sent 2 Sep · OPEN · follow-up 14 Sep

CRM · OPPORTUNITY 2614 · OPEN

QUOTE Q-2617 · Gothenburg · pump maker

ILLUSTRATIVE COMPANY RECORD

QUOTE Q-2617 · Gothenburg · pump maker

Conveyor and drying module

EUR 65,000 net · margin 24% (EUR 15,600)

Sent 7 Sep · OPEN · decision expected week 39

CRM · OPPORTUNITY 2617 · OPEN

Lyon · call 18 Aug

ILLUSTRATIVE COMPANY RECORD

Lyon · call 18 Aug

Customer's line stop is week 37 (7 to 13 Sep).

Both kits on site before then. Delivery 1 Sep agreed.

Partial delivery not wanted; see contract paragraph 4.

CRM · NOTE ON OPPORTUNITY 2611 · 2026-08-18 · ACCOUNT MANAGER

ORDER 4471 · Lyon · confirmed 18 Aug 2026

ILLUSTRATIVE COMPANY RECORD

ORDER 4471 · Lyon · confirmed 18 Aug 2026

2 x KIT-FR2210 filtration retrofit kit @ 17,900 = 35,800

Each kit requires 1 x FR-2210-B filter housing in its assembly

Commissioning, 1 day on site = 2,600

Net total EUR 38,400

Customer-site target 2026-09-01 · carrier collection at Aalen plant · contract 2026-0418

ERP · SALES ORDER 4471 · CONFIRMED 2026-08-18 14:05

OPERATIONS
EXHIBIT B · STOCK · FR-2210-B · filter housing, bag type, DN80

ILLUSTRATIVE COMPANY RECORD

EXHIBIT B · STOCK · FR-2210-B · filter housing, bag type, DN80

On hand 1 · reserved 2 housings for order 4471 · available -1

BOM demand: 1 housing per KIT-FR2210 retrofit kit; 2 kits required

Reorder point 4 · below it since 12 Aug · nothing ordered until 25 Aug

On order 3 · PO 5528 raised 25 Aug · supplier lead 9 working days · ETA 7 Sep

PM-0410 pump module · on hand 6 · reorder point 3 · OK

VS-118 valve set · on hand 14 · reorder point 8 · OK

ERP · STOCK LEDGER · SNAPSHOT 2026-09-04 08:00

PRODUCTION · LINE 2 · order 4471 kit assembly

ILLUSTRATIVE COMPANY RECORD

PRODUCTION · LINE 2 · order 4471 kit assembly

Slot W36 · planned Mon 31 Aug 08:00

HELD 25 Aug 16:10: FR-2210-B housings short 1 of 2

Re-slotted W37 · Mon 7 Sep 14:00, after goods receipt 11:20

Goods receipt: 3 housings; assembly consumes 2 into 2 KIT-FR2210 kits

Housing balance after assembly: 1 + 3 - 2 = 2, still below reorder point 4

Assembled 17:30 · packed Tue 8 Sep 07:50

ERP · WORK ORDER 4471-A · LINE 2

EXHIBIT A · CRM

ILLUSTRATIVE COMPANY RECORD

EXHIBIT A · CRM

Order 4471

DELIVERED

FINAL

Status set 1 Sep by the invoice sync

CRM · OPPORTUNITY 2611 · STATUS FIELD · 2026-09-04

EXHIBIT A · OPERATIONS

ILLUSTRATIVE COMPANY RECORD

EXHIBIT A · OPERATIONS

Order 4471

NOT SHIPPED

FINAL

Delivery note: none · slot held

ERP · DELIVERY NOTES FOR 4471: NONE · 2026-09-04

EXHIBIT A · FINANCE

ILLUSTRATIVE COMPANY RECORD

EXHIBIT A · FINANCE

Order 4471

UNPAID

FINAL

Invoice RE-26-0917 · EUR 38,400 · open

ERP AR · OPEN ITEMS · 2026-09-04

FINANCE
RECEIVABLES · 2026-09-10

ILLUSTRATIVE COMPANY RECORD

RECEIVABLES · 2026-09-10

61 open invoices · EUR 4.18M

Invoice age from issue date: 0 to 30 days 2.71M · 31 to 60 days 0.94M · 61 to 90 days 0.38M · over 90 days 0.15M

Flag: RE-26-0917 · Lyon · 38,400 · 9 days open

No delivery note supported its issue on 1 Sep. Carrier pickup was recorded on 8 Sep.

Invoice age is not the number of days overdue.

ERP AR · AGING REPORT · 2026-09-10 06:00

EXHIBIT C · INVOICE RE-26-0917 · order 4471 · Lyon

ILLUSTRATIVE COMPANY RECORD

EXHIBIT C · INVOICE RE-26-0917 · order 4471 · Lyon

EUR 38,400 net

Issued 1 Sep 2026 by the planned-delivery run

ERP due date 1 Oct: 30 days from invoice issue

Contract paragraph 4: 30 calendar days from confirmed receipt at the customer's site; a weekend due date moves to the next weekday

Status UNPAID · the contractual due date depends on confirmed customer receipt

ERP AR · INVOICE RE-26-0917 · AUTO-RUN 2026-09-01 02:00

CASH PLAN · 2026-09-10 07:00

ILLUSTRATIVE COMPANY RECORD

CASH PLAN · 2026-09-10 07:00

Bank-feed balance EUR 2.36M across two accounts

Remaining this week: in 0.41M expected · out 0.29M scheduled, supplier run Friday 11 Sep

Net forecast movement: +0.12M if those flows settle

Projected closing balance: EUR 2.48M if the stated flows settle and no other movements occur

RE-26-0917 · 38,400 · projected due Mon 12 Oct only if customer-site receipt is confirmed for Thu 10 Sep

Forecast assumes payment at the contractual due date; actual receipt and payment remain unconfirmed

Balance source: bank feed. Forecast inputs: open invoices, scheduled payments, contract paragraph 4 and carrier ETA.

BANK FEED · 2026-09-10 07:00 · TWO ACCOUNTS

THE HUMAN GATE
A PERSON DECIDES

ILLUSTRATIVE COMPANY RECORD

A PERSON DECIDES

Order 4471 · exception E-0931

Waits for: the operations lead

Raised 25 Aug 16:10 · decided 26 Aug 08:30

WORKFLOW · GATE M2 · OWNER OF RECORD: OPERATIONS LEAD

EXCEPTION E-0931 · order 4471

ILLUSTRATIVE COMPANY RECORD

EXCEPTION E-0931 · order 4471

FR-2210-B housings short 1 of 2 · PO 5528 ETA 7 Sep

A: propose a partial shipment; buyer consent and dispatch dates must be agreed

B: wait, ship both kits Tue 8 Sep · carrier arrival estimate Thu 10 Sep

The estimate misses the agreed 1 Sep date and the request for both kits before week 37 begins on 7 Sep

The operations lead must decide the internal route. A revised customer commitment requires the buyer's acceptance.

WORKFLOW · EXCEPTION E-0931 · RAISED 2026-08-25 16:10

INTERNAL DECISION · B

ILLUSTRATIVE COMPANY RECORD

INTERNAL DECISION · B

Wait. Ship both kits Tuesday 8 September.

Tell the customer today, with the proposed revised date. (Never sent.)

Buyer acceptance of the revised arrival date is not recorded

Basis: stock ETA and complete-shipment constraint; the original 1 Sep target and pre-week-37 requirement remain missed

The internal route was chosen. The customer handoff and revised-date approval remain unresolved.

WORKFLOW · DECISION E-0931 · OPERATIONS LEAD · 2026-08-26 08:30 · CUSTOMER NOTE NOT SENT

MODES · WHAT RAN, WHAT PAUSED · order 4471

ILLUSTRATIVE COMPANY RECORD

MODES · WHAT RAN, WHAT PAUSED · order 4471

M0 Observe · stock below reorder point · reported

M1 Propose · PO 5528 drafted · purchasing submitted it

M2 Gated · partial or complete shipment · operations lead chose B

M3 Policy-bound · carrier booking and sourced status reply ran on the internal route

That execution does not establish buyer acceptance of the revised arrival date

Open exception: customer notification and revised-date acceptance are not recorded

POLICY · ACTION REGISTER · REV 2026-08

THE RECEIPT
EXHIBIT D · CARRIER · PICKUP SCAN

ILLUSTRATIVE COMPANY RECORD

EXHIBIT D · CARRIER · PICKUP SCAN

Tue 8 Sep 2026 · 09:41 · Aalen plant

Consignment 44 0871 2265 3 · 2 pallets · 386 kg

ETA Lyon Thu 10 Sep

CARRIER MAIL · 2026-09-08 09:41 · SCAN EVENT

CONTRACT 2026-0418 · paragraph 4

ILLUSTRATIVE COMPANY RECORD

CONTRACT 2026-0418 · paragraph 4

Customer-site delivery target: 1 Sep 2026. Carrier collection at Aalen is arranged by the seller.

Payment: 30 calendar days from confirmed receipt at the customer's site, not from invoice issue or carrier collection.

For this illustrative contract, a due date on Saturday or Sunday moves to the next Monday.

Partial deliveries and a revised customer delivery commitment require the buyer's acceptance.

CONTRACT 2026-0418 · §4 · SIGNED 2026-08-18

RECEIPT · ORDER 4471

ILLUSTRATIVE COMPANY RECORD

RECEIPT · ORDER 4471

STATUS REPLY RECORDED

Collected Tue 8 Sep 09:41 · estimated arrival Thu 10 Sep; customer-site receipt not yet confirmed

Sources: sales order 4471 · carrier mail 09:41 · contract paragraph 4

Owner of the internal shipment decision: operations lead

Open: missed requested date, buyer acceptance of revised arrival, and confirmation of receipt

Illustrative time to answer: 41 s

RECEIPT 4471-R1 · 2026-09-08 09:47:55 · SOURCES ATTACHED

Where is my order?

ILLUSTRATIVE COMPANY RECORD

Where is my order?

Collected Tuesday. Expected with you Thursday, subject to the carrier's estimate.

The requested delivery date was missed; arrival confirmation is still pending.

Asked 09:47:14 · answered 09:47:55

CUSTOMER MAIL · 2026-09-08 09:47 · ANSWERED, SOURCES ATTACHED

CASE 0001
CASE 0001

CORE METHOD

CASE 0001

SYSTEM BOUNDARY REVIEW

FREE · FIXED SCOPE

Finds the first workflow worth changing.

Hands over: baseline and target · what the system may do, per action · the acceptance test your team reruns · the expand or stop decision

Request the review

CORE METHOD · THE FIRST ENGAGEMENT · FREE, FIXED SCOPE

No source, no answer.

CORE METHOD

No source, no answer.

REFUSAL CONTRACT · 1 OF 4

No authority, no action.

CORE METHOD

No authority, no action.

REFUSAL CONTRACT · 2 OF 4

No test, no handover.

CORE METHOD

No test, no handover.

REFUSAL CONTRACT · 3 OF 4

No invented answers.

CORE METHOD

No invented answers.

REFUSAL CONTRACT · 4 OF 4

THE WHOLE BOARD
GOVERNED AI INTEGRATION

CORE METHOD

GOVERNED AI INTEGRATION

Private knowledge, model and tool routing, policy-bound automation with configured approval gates, client-scoped memory, and verified learning.

LANE 1 · PRIVATE AI · RETRIEVAL · CONTROL PLANE

OPERATIONAL SOFTWARE AND DATA FOUNDATIONS

CORE METHOD

OPERATIONAL SOFTWARE AND DATA FOUNDATIONS

Decision applications, data rescue, CRM and ERP integration, review queues, audit, and reversible rollout.

LANE 2 · APPLICATIONS · DATA CONTRACTS · HANDOVER

AI SECURITY AND ASSURANCE

CORE METHOD

AI SECURITY AND ASSURANCE

Threat paths, prompt injection, credentials, egress, tool permissions, contamination, and client-rerunnable controls.

LANE 3 · BOUNDARIES · TESTS · RESIDUAL RISK

MEASUREMENT AND EVIDENCE SYSTEMS

CORE METHOD

MEASUREMENT AND EVIDENCE SYSTEMS

Connect sources, grade claims, repair measurement, and route strategy and production through evidence gates; marketing intelligence is its first application.

LANE 4 · SOURCES · CLAIMS · GATES

READING THE BOARD

CORE METHOD

READING THE BOARD

Red thread: connected context. Pins link related records and sections.

Read each source to inspect the evidence behind a claim.

Red triangle: a person decides.

Exhibits are lettered A to D.

LEGEND · THE TWO USES OF RED

ILLUSTRATIVE DATA

CORE METHOD

ILLUSTRATIVE DATA

The company on this board is fictional: about 180 people, one plant, customers across Europe.

No real company, person or customer record appears.

BOARD · ILLUSTRATION · 2026-09-10

Built systems and the evidence behind them

The evidence behind the practice

System records, their delivery scope, and the tests your team can run.

Practice register snapshot: 26 to 27 August 2026. The dates below belong to the original records.

Eight system records and their scope

Built means implemented at the stated scope. Verified reference identifies a tested reference implementation. Research identifies published work. Designed identifies architecture prepared for a future build.

Prospect intelligence engine Built

Governed AI integration / 27 August 2026

Sourced company discovery, deduplication, fit and buying-signal scoring, scheduled sweeps and operator feedback. Discovery and scoring are the built scope; outreach channels are configured for each client inside their rules.

Departmental knowledge system Built

Governed AI integration / 27 August 2026

Source-cited answers from documents and mail, human review queues, customer isolation and fail-closed writes. The recorded scope is one department; expansion proceeds department by department and permission by permission.

Customer-scoped relationship memory Built

Governed AI integration / 27 August 2026

CRM identities resolved into a governed customer container, with mail provenance, review lanes and retrieval that refuses cross-customer reads. Suppliers, partners and other counterparties are an expansion path, added source by source with permission.

Multi-model operations platform Built

Operational software and data foundations / 27 August 2026

The record describes daily use in our own operation: specialist workers, per-model costs, a policy-bound report with its receipt, and a security routine that remains report-only. Client deployments are configured connector by connector.

Tool and credential plane Verified reference

AI security and assurance / 26 August 2026

A controlled connection point with credentials held server-side, least authority and an append-only audit. The source records passing type, memory, orchestration and integrity probes on 26 August 2026. This status covers the reference implementation; each deployment requires its own probes.

Learning-organism program Research

AI security and assurance / 27 August 2026

Public research on code-checked claims, adversarial review, prediction ledgers scored against reality and typed abstention. Its scope is the research behind system testing and learning. The essays are linked in the writing register below.

Zero-egress finance architecture Designed

AI security and assurance / 27 August 2026

A reference architecture for open-weight models on client-owned hardware, gated external actions, a sealed audit journal and written acceptance tests. The recorded scope is designed and acceptance-specified. A build is scoped when an engagement requires this boundary.

Measurement and evidence desk Built / live at snapshot

Measurement and evidence systems / 27 August 2026

Claim grading, a measurement veto, attribution repair and adversarial quality checks. The record describes commercial operation in marketing; extension to other functions is a designed expansion path.

The marketing application of the measurement practice ↗

Read about the measurement diagnostic ↗

Six acceptance procedures your team can rerun

Acceptance register: 27 August 2026. These are proposed pass conditions to agree within an engagement's scope. They do not report completed tests on the fictional case.

E1 / The cable-pull test

Pass condition: the agreed functionality remains available after the network path is removed, on a boundary your own packet capture verified.

E2 / No action exceeds its authority

Pass condition: a pre-authorized action executes and records its result without manual approval; the same action designated as gated cannot execute until the authenticated human channel approves, enforced at the role and database layers. Both routes reconstruct from their authorization basis.

E3 / Stop or ask when evidence is missing

Pass condition: low-confidence input follows the configured stop or human-review route, and the rate appears in the run report. This is the workflow's typed abstention test.

E4 / Inspect and reconstruct

Pass condition: any controlled action reconstructs from its record: input, policy version, model and prompt version, the authorization basis (policy version or authenticated approval), and the result, on an append-only, hash-chained journal.

E5 / The blocked number

Pass condition: a figure without provenance cannot reach a report; the gate blocks it and names the reason.

E6 / The exit drill

Pass condition: with all our access disabled, your team rebuilds the system from escrowed, hash-pinned artifacts using the runbook.

The writing register

Three essays from the source register, linked to their canonical pages on the studio research shelf.

Read the illustrative customer file

Lyon / Hydraulic components

Industrial hydraulics France

As of 08 Sep 2026, 09:48

Customer since
2021
Orders placed
1817 completed · 1 active
Net ordered value
286,400

NEEDS ATTENTION

Delivery update requested.

The answer is sent. Confirm the impact of the late arrival, then confirm receipt.

The relationship behind the order.

A returning customer with 17 completed orders before this retrofit. Their production shutdown makes delivery timing the immediate priority.

Satisfaction
No satisfaction feedback recorded
Customer constraint
Production line stop, 7 to 13 Sep
Timing risk
Expected arrival misses the agreed date and the request for both kits before the shutdown.

Order 4471

Net value
€38,400
Shipment
Collected by carrier
Expected arrival
10 Sep 2026 Carrier estimate
Invoice
Open, not overdue

Conditional payment forecast: 12 Oct, assuming confirmed receipt on 10 Sep and payment on the contractual due date. Actual arrival and payment remain unconfirmed.

The latest thread.

08 SEP 2026

  1. Collected at Aalen

    Two pallets, 386 kg. Expected in Lyon on Thursday.

    CARRIER / PICKUP SCAN
  2. The customer asks for an update

    “Where is my order?” The agreed 1 September date has passed.

    CUSTOMER MAIL / INCOMING
  3. An answer leaves with its sources

    Pickup confirmed. Thursday arrival remains the carrier's estimate.

    RECEIPT 4471-R1 / SOURCES ATTACHED
How this summary was formed
Recorded facts
Sales order 4471 establishes the €38,400 commitment. The carrier scan records pickup on 8 Sep at 09:41. Customer mail and receipt 4471-R1 record the question and sourced reply.
Attention flag
The expected arrival misses the promised date and the requested pre-shutdown deadline. Sending an answer does not close this exception: acceptance of the revised date and confirmation of arrival are both absent.
Satisfaction
The available messages show a delivery question and a sourced reply, not a satisfaction response. No sentiment score is assigned.
Payment timing
Invoice RE-26-0917 is open. The illustrative contract sets payment 30 calendar days after confirmed customer-site receipt and moves weekend due dates to the next weekday. Receipt on 10 Sep would make 12 Oct the due date. This is a conditional forecast, not an observed payment or the earliest possible receipt of cash.

The relationship ledger

The history below is an illustrative addition to this customer file. It describes ordered value, not collected revenue.

Completed orders before order 4471
PeriodOrdersNet EUR
2021224,000
2022339,500
2023344,000
2024348,750
2025350,750
2026 through 17 Aug341,000
Completed17248,000

17 completed orders + active order 4471 = 18 orders. €248,000 + €38,400 = €286,400 net ordered value.

ILLUSTRATIVE CUSTOMER FILE

A fictional account, showing how a relationship can be read through its records.

AN ILLUSTRATIVE COMPANY CASE

An illustrative company record.

CORE METHOD / THE PRACTICE

The company
as a connected system.

We design, build and hand over AI assistants, operational software and governed workflows. Start with one bounded job, measure what changed, then decide what deserves to grow.

Governed AI integration

Private knowledge, model and tool routing, client-scoped memory and verified learning.

Operational software and data foundations

Decision applications, CRM and ERP integration, review queues and reversible rollout.

AI security and assurance

Threat paths, tool permissions, data boundaries and controls your team can rerun.

Measurement and evidence systems

Connect sources, grade claims and repair the measurements behind decisions.

What a handover includes

Named owners, documented boundaries, acceptance tests, a rollback path and the evidence needed to operate the work. Scope and acceptance criteria are agreed before implementation.

The evidence behind the practice

System records, their delivery scope, and the tests your team can run.

Practice register snapshot: 26 to 27 August 2026. The dates below belong to the original records.

Eight system records and their scope

Built means implemented at the stated scope. Verified reference identifies a tested reference implementation. Research identifies published work. Designed identifies architecture prepared for a future build.

Prospect intelligence engine Built

Governed AI integration / 27 August 2026

Sourced company discovery, deduplication, fit and buying-signal scoring, scheduled sweeps and operator feedback. Discovery and scoring are the built scope; outreach channels are configured for each client inside their rules.

Departmental knowledge system Built

Governed AI integration / 27 August 2026

Source-cited answers from documents and mail, human review queues, customer isolation and fail-closed writes. The recorded scope is one department; expansion proceeds department by department and permission by permission.

Customer-scoped relationship memory Built

Governed AI integration / 27 August 2026

CRM identities resolved into a governed customer container, with mail provenance, review lanes and retrieval that refuses cross-customer reads. Suppliers, partners and other counterparties are an expansion path, added source by source with permission.

Multi-model operations platform Built

Operational software and data foundations / 27 August 2026

The record describes daily use in our own operation: specialist workers, per-model costs, a policy-bound report with its receipt, and a security routine that remains report-only. Client deployments are configured connector by connector.

Tool and credential plane Verified reference

AI security and assurance / 26 August 2026

A controlled connection point with credentials held server-side, least authority and an append-only audit. The source records passing type, memory, orchestration and integrity probes on 26 August 2026. This status covers the reference implementation; each deployment requires its own probes.

Learning-organism program Research

AI security and assurance / 27 August 2026

Public research on code-checked claims, adversarial review, prediction ledgers scored against reality and typed abstention. Its scope is the research behind system testing and learning. The essays are linked in the writing register below.

Zero-egress finance architecture Designed

AI security and assurance / 27 August 2026

A reference architecture for open-weight models on client-owned hardware, gated external actions, a sealed audit journal and written acceptance tests. The recorded scope is designed and acceptance-specified. A build is scoped when an engagement requires this boundary.

Measurement and evidence desk Built / live at snapshot

Measurement and evidence systems / 27 August 2026

Claim grading, a measurement veto, attribution repair and adversarial quality checks. The record describes commercial operation in marketing; extension to other functions is a designed expansion path.

The marketing application of the measurement practice ↗

Read about the measurement diagnostic ↗

Six acceptance procedures your team can rerun

Acceptance register: 27 August 2026. These are proposed pass conditions to agree within an engagement's scope. They do not report completed tests on the fictional case.

E1 / The cable-pull test

Pass condition: the agreed functionality remains available after the network path is removed, on a boundary your own packet capture verified.

E2 / No action exceeds its authority

Pass condition: a pre-authorized action executes and records its result without manual approval; the same action designated as gated cannot execute until the authenticated human channel approves, enforced at the role and database layers. Both routes reconstruct from their authorization basis.

E3 / Stop or ask when evidence is missing

Pass condition: low-confidence input follows the configured stop or human-review route, and the rate appears in the run report. This is the workflow's typed abstention test.

E4 / Inspect and reconstruct

Pass condition: any controlled action reconstructs from its record: input, policy version, model and prompt version, the authorization basis (policy version or authenticated approval), and the result, on an append-only, hash-chained journal.

E5 / The blocked number

Pass condition: a figure without provenance cannot reach a report; the gate blocks it and names the reason.

E6 / The exit drill

Pass condition: with all our access disabled, your team rebuilds the system from escrowed, hash-pinned artifacts using the runbook.

The writing register

Three essays from the source register, linked to their canonical pages on the studio research shelf.

Read the research ↗ Visit the studio ↗

CASE 0001 / FREE, FIXED SCOPE

Find the first
connection.

Tell us where work gets stuck. We will use it to frame your System Boundary Review.

We use your details to answer this request. Privacy notice

Prefer email? vision@coremethod.studio ↗

ILLUSTRATIVE CUSTOMER FILE / 01

Lyon / Hydraulic components

Industrial hydraulics France

As of 08 Sep 2026, 09:48

Customer since
2021
Orders placed
1817 completed · 1 active
Net ordered value
286,400

NEEDS ATTENTION

Delivery update requested.

The answer is sent. Confirm the impact of the late arrival, then confirm receipt.

The relationship behind the order.

A returning customer with 17 completed orders before this retrofit. Their production shutdown makes delivery timing the immediate priority.

Satisfaction
No satisfaction feedback recorded
Customer constraint
Production line stop, 7 to 13 Sep
Timing risk
Expected arrival misses the agreed date and the request for both kits before the shutdown.

Order 4471

Net value
€38,400
Shipment
Collected by carrier
Expected arrival
10 Sep 2026 Carrier estimate
Invoice
Open, not overdue

Conditional payment forecast: 12 Oct, assuming confirmed receipt on 10 Sep and payment on the contractual due date. Actual arrival and payment remain unconfirmed.

The latest thread.

08 SEP 2026

  1. Collected at Aalen

    Two pallets, 386 kg. Expected in Lyon on Thursday.

    CARRIER / PICKUP SCAN
  2. The customer asks for an update

    “Where is my order?” The agreed 1 September date has passed.

    CUSTOMER MAIL / INCOMING
  3. An answer leaves with its sources

    Pickup confirmed. Thursday arrival remains the carrier's estimate.

    RECEIPT 4471-R1 / SOURCES ATTACHED
How this summary was formed
Recorded facts
Sales order 4471 establishes the €38,400 commitment. The carrier scan records pickup on 8 Sep at 09:41. Customer mail and receipt 4471-R1 record the question and sourced reply.
Attention flag
The expected arrival misses the promised date and the requested pre-shutdown deadline. Sending an answer does not close this exception: acceptance of the revised date and confirmation of arrival are both absent.
Satisfaction
The available messages show a delivery question and a sourced reply, not a satisfaction response. No sentiment score is assigned.
Payment timing
Invoice RE-26-0917 is open. The illustrative contract sets payment 30 calendar days after confirmed customer-site receipt and moves weekend due dates to the next weekday. Receipt on 10 Sep would make 12 Oct the due date. This is a conditional forecast, not an observed payment or the earliest possible receipt of cash.

The relationship ledger

The history below is an illustrative addition to this customer file. It describes ordered value, not collected revenue.

Completed orders before order 4471
PeriodOrdersNet EUR
2021224,000
2022339,500
2023344,000
2024348,750
2025350,750
2026 through 17 Aug341,000
Completed17248,000

17 completed orders + active order 4471 = 18 orders. €248,000 + €38,400 = €286,400 net ordered value.

YOUR COMPANY / CONNECTED CONTEXT

Every record has
something to add.

Bring the sources relevant to one workflow into a shared operating view. The connections and permissions are defined for your business.

Customers and relationships

CRM records, quotes, contracts, correspondence, call notes, support cases, renewals and customer feedback.

Finance and commitments

E-invoices, credit notes, payments, bank reconciliation, purchase orders and agreed commercial terms.

Stock across locations

Warehouse and country-level availability, reservations, goods receipts, supplier commitments and replenishment lead times.

Shipping and delivery

Carrier pickups, tracking events, expected arrivals, proof of delivery, returns and warranty claims.

Demand and performance

Website analytics, search demand, campaign results, enquiry sources and the revenue records used to check attribution.

Production and system health

Work orders, quality exceptions, maintenance records, access changes and failed automation runs.

Start with a question your company needs to answer. Connect the records that can answer it.