Version: v0_1 Date: 2026-06-26 Status: Working draft (investigation) Author: Marvin Percival (DUNIN7) Anchored to: Loomworks candidate seed v0.12 (2026-06-07) Companion to: cognisee-loomworks-positioning-v0_3 (the competitive read — still stands)
The earlier note read Cognisee as a competitor: same diagnosis of the tacit- knowledge problem, opposite response (they extract into a model, Loomworks preserves with provenance). This note holds a different reading the Operator raised: Cognisee and Loomworks as a two-way knowledge exchange, not rivals.
In the seed's terms, Cognisee becomes a referenced domain — a body of practice a Loomworks engagement reaches for material — and Loomworks Memory becomes a feedstock Cognisee can consume. The two directions are not symmetric, and the asymmetry is the point: Cognisee needs what Loomworks produces more than the reverse, because a reasoner is only as good as its feedstock and provenance-preserved Memory is premium feedstock.
What's in scope: how each direction maps to the seed's Memory model, where the seed governs it cleanly, and one genuine boundary tension to surface. What's out of scope: any build work, any integration design, any commercial-terms discussion. This is a positioning investigation, not a plan.
Prior position (positioning note v0.3): Cognisee is a competitor. Same diagnosis, opposite response. They build a collective brain that reduces the need to consult the expert; Loomworks builds a provenance-preserving commons that keeps the expert in authority.
This note's reading (Operator-raised): "opposite response" does not have to mean "competitor." It can mean complementary layer. Cognisee does extraction-into-a-reasoner; Loomworks draws on the output as one referenced domain among several, and can in turn supply Cognisee with a better grade of input than raw extraction yields.
Both readings can be true at once. v0.3 is the competitive read; this is the complementary read. They are not in conflict — a company can be a competitor on one axis and a resource on another. This note does not retire v0.3; it sits beside it.
The seed (v0.12) gives Memory two independent access axes on every scope above the engagement: reach (who may draw on it) and contribution (who may write into it). Reach is open by default; contribution to a shared scope is gated. The two directions of the Cognisee exchange land on these two axes — and that is why they are not symmetric.
Cognisee sits as a referenced domain. The seed already has the slot: an engagement "references" a set of domains, "peers to one another, each for its own kind of knowledge," and reach is "open by default." Cognisee becomes one such domain — a body of tacit-knowledge practice an engagement reaches for material.
What comes back from a reasoner is an inference. The seed's provenance rule governs how it lands: a contribution "carries who contributed it, when, how — typed, spoken, extracted from a document." Cognisee-sourced material enters Loomworks Memory marked as Cognisee-derived, origin preserved. The Operator stays in authority over whether it is admitted (operator-authority over state transitions; the trusted-core admit gate for anything entering a shared scope).
The seed handles this direction without strain. Reach is open; provenance marks the origin; the Operator admits. Nothing new is required at the seed level. (How an external reasoner is registered as a reference-able domain is specification-level and not settled here.)
This is where the asymmetry bites, and it is Loomworks's advantage.
Cognisee wants tacit knowledge as training feedstock. Loomworks holds exactly that — but holds it **with provenance, with corrections preserved, with trajectory intact**. That is a materially better feedstock than raw extraction, because it carries the thing extraction throws away:
contribution. A retraction is a contribution. Both are preserved.")
A reasoner trained on provenance-preserved memory has access to the shape of how knowledge formed, not just its final state. That is a higher-grade input than undifferentiated text scraped from documents.
But the seed's contribution axis is explicit: shared scopes are "gated on contribution… a contribution from anyone outside the trusted core is held until a member of the trusted core admits it or turns it away." Flowing Loomworks Memory out to Cognisee is a contribution event to an external consumer, and it follows the same posture: **deliberate, recorded, operator-authorized — not a default.**
So, stated precisely:
> **Loomworks reaches Cognisee freely (open reach) and contributes to Cognisee > deliberately (gated, operator-authorized, provenance-marked).**
That is not a hedge. It is the seed's exact open-reach / gated-contribution model, applied to an external domain.
The relationship is not "Cognisee is a resource for us." It is "each is a resource for the other, but Loomworks holds the scarcer half."
A reasoner is only as good as its feedstock. Provenance-preserved engagement memory is premium feedstock — scarce, hard to manufacture, and exactly what an extraction engine cannot generate for itself. Loomworks's provenance discipline, which v0.3 framed as a philosophical difference from Cognisee, turns out to also be a commercial asset to Cognisee.
This inverts the Operator's opening phrasing in a useful way. Cognisee becoming "a resource for Loomworks knowledge" is the visible half. The less obvious and more valuable half is that Loomworks is a premium resource for Cognisee — and holds the side of the exchange that is harder to replace.
The seed's strongest commitment is that origin is marked and corrections are preserved — "AI origin marked non-suppressibly," provenance walkable, trajectory kept.
If Loomworks Memory flows into Cognisee's model and is dissolved into weights, the provenance dies on the other side of that boundary — by Cognisee's design, not Loomworks's. Loomworks can mark what it sends and record that it sent it. It cannot make Cognisee preserve that provenance downstream.
This is not a blocker. It is a boundary condition, and it sits at exactly the seam where two of Loomworks's commitments meet:
preserved by the consumer)
The Operator should see this tension rather than have it smoothed. It does not prevent the exchange. It does mean the outbound direction is a deliberate, recorded, provenance-marked-at-departure act — which is exactly what the seed's gated-contribution posture already requires. The seed's discipline and this tension point the same way: outbound is gated, not default.
no adapter, no domain-registration mechanism is designed here.
Specification-level; comes due if and when the domain layer (C5) builds toward external references.
reciprocal arrangement, or nothing — out of scope.
seed-coherent and asymmetric in Loomworks's favor. Whether to act on it is the Operator's decision, not this note's recommendation.
(see v0.3 caveat). They may not want external feedstock; their framework is not public. Recheck after their launch.
Cognisee as competitor on the authority and commons axes. This note adds the complementary read; it does not replace the competitive one.
two-way scope exchange per the Operator's reading. Maps both directions to the seed's reach/contribution axes, names the asymmetry favoring Loomworks, and surfaces the provenance-at-the-boundary tension. Companion to, not replacement of, positioning note v0.3.
DUNIN7 — Done In Seven LLC — Miami, Florida Cognisee as a Referenced Domain — Two-Way Scope Relationship Investigation — v0.1 — 2026-06-26