Intertween.*
ENSV
Intertween reference library Documentation, sources and later decisions →
ROADMAPFROM SPECIFICATION TO REUSE

PRESERVE / REUSE / LEARN

Build institutional learning through every reuse.

Intertween connects knowledge to the contexts in which it is used and the outcomes that follow. The roadmap begins with one useful knowledge journey and grows toward learning that can travel safely between organisations.

Follow the value cycle ↓
THE LEARNING CYCLE

Each use should leave the knowledge system richer.

The protocol creates continuity between a source, its use in a new context and the evidence produced afterwards. Value grows when experience can return without overwriting the original.

01 / PRESERVE

Create a reusable object

Keep knowledge connected to its source, meaning, rights, uncertainty and responsible context.

VALUE · Less knowledge is lost when files, systems, projects or teams change.
02 / APPLY

Reuse it where work happens

Bring a permitted projection into another workflow or context while local interpretation and authority remain visible.

VALUE · Existing knowledge reduces repeated work without becoming detached from its conditions.
03 / RETURN

Connect outcomes and corrections

Record what changed, what worked, what failed and which adaptations were needed, then link that evidence back to the reused object.

VALUE · The next use begins with accumulated and inspectable learning.
Reuse is not the end of the knowledge lifecycle. It is where new learning begins.
THE PRACTICAL SHIFT

From stored information to reusable organisational memory.

The present phase establishes the Knowledge Object through Wrapper, Mapper and Tracker. The first pilot follows one complete journey across two governed contexts. A later pilot shows that the same learning loop can work between independently operated nodes.

The specification defines the contract. Existing tools can implement it. Adapters connect it to federation infrastructure.
Protocol NODE

A Local protocol client is one implementation option.

OPTIONAL PARTICIPATION LAYER

<Client>

Participation

Proposes, explains, requests and presents Knowledge Objects in the flow of work.

→
{LOCAL KNOWLEDGE}

<Runtime>

Memory

Maintains objects, relationships, provenance, indexes, audit history and local policy state.

→
#RIGHTS / !PURPOSE

<Gateway>

Enforcement

Evaluates identity, purpose, rights and disclosure before anything crosses a node boundary.

These responsibilities may be delivered by a dedicated protocol node or embedded in existing applications, organisational gateways and data-space infrastructure such as Simpl.

THE CLIENT LOOP

Distribution becomes a governed part of ordinary work.

01

Recognise

Notice when daily work has produced knowledge worth preserving.

02

Prepare

Turn a document, decision or outcome into a candidate Knowledge Object.

03

Govern

Set provenance, validation, audience, purpose and reuse conditions.

04

Circulate

Publish only the projection that another node is permitted to discover or use.

05

Reuse

Bring trusted knowledge from the federation into the local working context.

06

Return

Connect adaptations, outcomes and corrections to the object that enabled them.

SPECIFICATION SEQUENCE

Make each layer testable before federation expands.

01

Stabilise the core

Freeze Knowledge Object identity and define Entity Reference, Representation, Assertion, Event, Participation, Actant Role and Projection.

02

Bind sources and payloads

Specify retrieval, hashes, custody, transformations, availability and representation-level policy.

03

Formalise composition

Complete Ledger, Knowledger, projection and ODRL contracts with semantic conformance tests.

04

Prove two-node circulation

Negotiate one purpose-bound projection, enforce masking, record reuse and return one correction or outcome.

05

Establish trust

Define node identity, key rotation, revocation, aggregation controls, compatibility and open stewardship.

06

Grow implementations

Support independent clients, runtimes, gateways, connectors and managed providers without weakening exit rights.

ONE AGORA / MANY VIEWS

Federate projections, not assumptions.

Nodes participate in one logical Agora without receiving one common view. The authoritative object remains with its originating node. A request can result in metadata, a reference, an anonymised pattern, a bounded summary or a fuller representation—depending on identity, purpose, mandate, sensitivity and rights. Every exchange records its protocol version, policy decision, evidence basis, resolved inputs and unavailable sources.

[authoritative object]
          ↓
@requester + !purpose
          ↓
#rights + {sensitivity}
          ↓
[permitted projection]
          ↓
#federated reuse
FEDERATION PROOF / AFTER THE FIRST PILOT

Two independent nodes. One governed knowledge journey.

NODE A
creates + validates→KO-001
becomes discoverable→NODE B
requests + reuses→KO-002
returns an outcome

The first two-context implementation establishes the learning loop locally. A later federation pilot adds independent node operation, policy-controlled projection, cross-node discovery, mandate-bound reuse, attribution and returned learning.

PILOT QUESTION

Does reuse create visible and usable learning?

The practical test is whether a source, its local interpretation, the decision to reuse it and the resulting outcome remain connected across contexts.

01

Continuity

Can every decision and activity be traced back to observations, assumptions and scenarios?

02

Epistemic clarity

Can a reviewer distinguish what was observed, assumed, inferred, decided and validated?

03

Local autonomy

Can two organisations compare interpretations without replacing their local concepts or authority?

04

Selective disclosure

Can a node expose a useful projection without revealing restricted source material or inferred sensitive patterns?

05

Returned learning

Can outcomes, corrections and contradictions update the shared knowledge graph without rewriting history?

06

Human control

Can an authorised reviewer inspect, contest, interrupt and reverse agent-supported actions?

07

Visible contribution

Can the pilot show whose contribution affected reuse, including work outside formal ownership?

08

Plural value

Can quantitative effects and qualitative change remain connected to context and evidence without becoming one score?

Research, trend analysis and domain evidence can support a problem definition. They do not validate the protocol's architecture, policy semantics or federation behaviour. Those claims remain hypotheses until tested through observable pilot evidence.
DATED MILESTONES

Conformance grows through evidence.

01 / 05 SEP 2026

Protocol alignment

Custody and emergent ownership separated; legal, jurisdiction and classification fields introduced; Level 0 drafted.

02 / Q4 2026

Level 0 candidate

Publish schema, JSON-LD context, conformance fixtures and the legal-mapping review process.

03 / Q1 2027

Two-node evidence

Complete one governed reuse journey and one unclaimed Intertween case with human review.

04 / AFTER PILOT

Federation candidate

Specify signed exchange, revocation, connector adapters, returned learning and reciprocity only after pilot evidence.

Dates are targets, not commitments. A milestone is complete only when its named conformance evidence is public and reproducible.
START A LEARNING JOURNEY

Reuse one thing and follow what happens.

Dialogue and further workTest the Intertween viewer →