Knowledge Commons Layer: bringing the archive design forward

[Argocyte]

Background

The archive contains docs/archive/Iskander Knowledge Commons (IKC).odt — a design document that predates the current architecture. The NLNet application describes the knowledge commons as a long-term outcome, positioned beyond Phase B.

This thread is the right place to bring that document forward into the current architectural context and decide what to carry forward, rather than opening an issue for work that isn't yet scoped.

Questions for discussion

1. What does the archive IKC document say that still applies? The current architecture has added Glass Box, IPFS anchoring (issue feat(legal-bridge): Nextcloud-native governance document lifecycle with ICN provenance #113 via Nextcloud), the curator network spec (docs/archive/curator_network_spec.txt), and the sovereign data fabric spec. How much of the IKC design is already covered by these?

2. Where does the knowledge commons sit in the scope model? The ICN architecture uses Self/Cooperative/Community/Federation/Commons scopes. The commons scope is the outermost layer — is the knowledge commons the implementation of that scope layer, or something narrower?

3. What is the relationship to Valueflows? The DisCO model tracks labour and economic events. The knowledge commons presumably tracks knowledge assets — curation, attribution, access, provenance. Is there a Valueflows-compatible model for knowledge assets, or does this require extension?

4. What is the earliest Phase this work could realistically begin? The application suggests post-Phase B. Is that still the right framing?

Next step

If this thread produces enough clarity to scope a Phase B or Phase C design issue, open one. If the archive document needs to be converted to a working doc and brought into docs/, that is a separate small task.

[Argocyte]

Phase C.5 coordination — 2026-04-11

Cross-reference: Phase C.5 Estates Warden (#138) manages the physical-commons layer (buildings, tools, vehicles) which is a complementary layer to the knowledge commons. Librarian agent evolution (see this discussion) and Estates Warden share the Nextcloud document storage backend for receipts, contracts, and policy documents.

[Argocyte]

Update 2026-04-12: The knowledge commons layer now has a dedicated repo: Argocyte/Iskander-data (CC-BY-SA 4.0 + AGPL-3.0). Bootstrapped with SCHEMA.md (6 streams: labour, decisions, tensions, membership, treasury, commons contributions), owners.jsonl, and dual-licence. The data commons will eventually migrate to decentralised storage (IPFS + DID signatures) per A8 direction. MVM (Multiple Variable Monitoring) will produce task-effort records as a new stream (D4/D12). — Et

[Argocyte]

Update: Knowledge Commons Architecture in Iskander-Code

The knowledge commons is now structurally implemented:

Tools commons (tools/): 20 shared tool definitions as JSON. Each agent links to ets permitted tools via resources/tools/.

Skills commons (tools/skills/): 24 skills mapped to ICA principles. Each skill declares applicable_agents and applicable_principles.

Agent commons (designed, not yet persisted): AgentSessionRegistry tracks all agent configurations. The cooperation (P6) agent curates the commons, the archivist (background) saves to et.

Weighted ranking: Newer agents complement older ones (versioned). Weights based on feminist economics 3 labour values. The researcher (P1) searches the commons for task-specific agents to clone.

Security: Values Council assessment required before skills enter the commons (ClawHub purged 2,419 malicious skills in 2026).

The 16-ecosystem research identified 1-3M tokens savings per new cooperative joining with a pre-populated commons. See Discussion #201.