Glossary · Version 2 · July 2026

The vocabulary of the Organizational Commons

The framework's own terminology: what is confirmed, what remains in the candidate bank for future development, and what was discarded and why — so as not to reopen a settled discussion without memory of the reason.

Internal technical names (proyectos, backlog, service_desk) don't change — they remain the field names in the code. This glossary defines the vocabulary used to speak about the framework externally: in proposals, presentations, and conversation with clients.

A · Confirmed

Terms in use

Organizational Commons

The complete framework: the methodology of decentralizing access to organizational information via conversational AI.

Umbrella name — everything else hangs from it.

Commons Farm

The central layer of consolidated data of a domain (Technology, Finance, HR). Technically a datamart/data lake, but without using those words externally.

Replaces "datamart" in external language. The schema's technical name doesn't change in the code.

Commons Chat

Conversational text access channel — the conversational surface that queries the Commons Farm.

First channel built.

Commons Team

The group of roles responsible for sustaining a domain's Commons Farm: information access and the evolution of the AI that operates it.

Renamed from "Center Team" in v2 — it ties the team to the Commons and avoids the "center = central control" connotation. It is established and launched in the third stage of the Commons lifecycle.

Curator

Commons Team role — decides what information enters the Commons and at what access level.

Sensor

Commons Team role — detects new signals from the business or the environment that should be incorporated.

Custodian

Commons Team role — responsible for the quality and currency of the data once consolidated.

Access by nature of information

Access principle: the access level of a piece of data is defined by what kind of information it is, not by the hierarchy of who asks.

Replaced "privacy by nature" in the v5 corpus.

Opening cycles

Transitional device: data opens progressively cycle by cycle, rather than demanding full transparency from day one.

Complements the access-by-nature principle.

OC Architect

Certification/role — not a purchasable product; it emerges from working with Adaptant on a project or as a partnership condition. Forms the Commons Team and transfers the operation to it.

Analogous to Atlassian's distribution model.

OC Lite

Excel-based skill — a demand entry point, not a replacement for the OC Architect.

B · Under evaluation

Candidate bank

Not confirmed. Access channels additional to Commons Chat, conceived with the same naming logic — none has been built yet.

Term	What it would be	English
Commons Voice	The same commons, but by voice	Commons Voice
Commons Radar	Proactive/active layer — alerts that surface on their own instead of waiting for a question (C4b layer)	Commons Radar
Commons Brief	Periodic summary for those who prefer to read rather than ask	Commons Brief
Commons Desk	Version embedded inside another tool (Slack, Teams)	Commons Desk
Commons Sense	Periphery capture channel — the double meaning is an asset: common sense / the Commons' sensing	Commons Sense
Commons Signals	Periphery capture channel — literal and transparent; "periphery signal" is already the pipeline's term	Commons Signals

Alternative metaphors for the data layer, evaluated but not chosen — kept in case it's worth varying the name for a specific domain (for example, if "Farm" doesn't fit a banking context).

Term	Metaphorical line	English
Commons Yard	Industrial — a place where what arrives from different origins is consolidated	Commons Yard
Commons Well	Water — the well from which what's needed is drawn	Commons Well
Commons Grove	Organic — more cultivated forest than farm	Commons Grove
Ejido	Agrarian — communal land, with its own regional root	—
Cauce	Water — the channel through which information flows (Weichselbaum's flow-vs-batch logic)	—
Substrate	Geological — the base layer on which everything else grows	Substrate
Granary	Agrarian — value accumulated and stored for when it's needed	Granary

C · Discarded

With reason — don't reopen without a new one

Term	Why it was discarded
Acervo	Discarded by direct preference, in favor of keeping "Commons" as the root of every name of the central layer.
DataFarm	Keeps the word "Data" up front — returns to the problem it wanted to avoid (sounding like generic IT vocabulary).
CoreData	Brand collision — Apple's data-persistence framework on iOS/macOS.
DataCore	Brand collision — DataCore Software, a storage-virtualization vendor with a presence in LATAM.
SmartCore	Generic — a home-automation/IoT product category, adds no distinct identity.
Commons Core	Phonetic collision with Common Core, the U.S. education standards, at times politically sensitive.
Datamart / Data lake / BI	Kept as internal technical vocabulary, but avoided in conversation with clients — that's what Commons Farm is for.
Silo	Never use as a synonym for repository — in management English "silo" names exactly the problem the Commons solves.

"Commons Chat queries the Technology Commons Farm."

That's the level of naturalness any new phrase added to this glossary has to have — if it needs explaining the first time someone hears it, it's probably not ready for external vocabulary yet.