AIFC-011: Operational DNA

Status: Draft 0.1 Standard: AI-First Community Standard Short name: AIFC Related to:

AIFC-000: Manifesto for AI-First Communities
AIFC-001: Core Concepts
AIFC-002: Community Model
AIFC-003: Values and Purpose
AIFC-004: Feedback and Change Proposals
AIFC-010: Knowledge Structure

Purpose of this document: Define Operational DNA as the critical part of a community knowledge base, describe its content, value, risks, protection, and relationship to AI, the Source of Truth, the Human Cockpit Layer, and Company as a System.

1. Purpose of this document

This document defines Operational DNA.

An AIFC knowledge base contains many types of knowledge. Some knowledge is supporting, some operational, some historical, and some critical.

Operational DNA is the part of the knowledge base that describes how the community actually functions, decides, creates value, learns, protects its boundaries, and replicates its capabilities.

In a company context, Operational DNA may contain the most valuable know-how:

how the company creates value,
how it decides,
how it works with customers,
how it organizes work,
how it manages quality,
how it uses AI,
how it protects know-how,
how it holds values,
how it learns,
how it differs from competitors.

Operational DNA is not only documentation.

It is the operational genetic code of the community.

2. Core principle

The core principle of this document is:

The better a community describes how it works, the more valuable its knowledge becomes, and the more carefully it must be protected.

AIFC therefore says:

Knowledge base is memory.
Operational DNA is critical capability.

3. Definition

Operational DNA is the critical part of the knowledge base that describes the community’s real operating model.

It includes knowledge, rules, decisions, workflows, skills, value interpretations, AI involvement, fallbacks, and relationships that allow the community to create value and continue its purpose.

Operational DNA answers questions such as:

How does the community actually function?
How does it create value?
How does it decide?
Which capabilities are critical?
Which know-how must it not lose?
Which workflows hold its operation together?
Which skills must people have?
Which AI skills do agents use?
Which parts of work can be replicated?
Which parts are sensitive or competitively important?
What would allow another entity to imitate the community?

4. Operational DNA vs ordinary knowledge

Not every piece of knowledge in the knowledge base is Operational DNA.

Ordinary knowledge

Ordinary knowledge may be:

general guidance,
note,
meeting summary,
list of links,
historical document,
simple description,
one-time output.

It may be useful, but it does not necessarily determine the community’s ability to operate.

Operational DNA

Operational DNA contains knowledge without which the community loses part of its operational capability.

It may include, for example:

decision logic,
critical workflows,
customer know-how,
architectural principles,
unique delivery model,
pricing logic,
security rules,
AI agentic workflows,
fallback modes,
human skills,
AI skills,
governance rules,
relationships between values and decisions,
learning mechanisms,
Community Interface.

Minimum requirement

An AIFC community must be able to distinguish ordinary knowledge base content from Operational DNA.

Operational DNA must be classified as a critical asset.

5. Why Operational DNA matters

Operational DNA matters for three reasons.

5.1 It makes the community understandable

Well-described Operational DNA allows new members, leaders, auditors, and AI agents to understand how the community works.

It reduces dependency on oral transfer, hidden know-how, and individuals.

5.2 It makes the community improvable

What is described can be analyzed. What is analyzed can be improved. What is improved can be written back to the Source of Truth.

Operational DNA is the basis for systematic improvement.

5.3 It makes the community replicable

A well-described operating model can be transferred, forked, licensed, audited, or used to create a new community or company.

This is both an opportunity and a risk.

If Operational DNA leaks, it is not only documentation that leaks. Capability leaks.

6. Components of Operational DNA

Operational DNA may contain the following areas.

purpose and values
strategy and operating model
decision logic
critical workflows
human skills
AI skills
customer and stakeholder knowledge
quality model
risk and security rules
AI governance
fallback and recovery modes
feedback and learning loops
community interfaces
business model
delivery model

These areas do not have to be in one document. They may be distributed across the Source of Truth.

What matters is that they are recognizable, protected, and maintained.

7. Purpose and values as DNA

Purpose and values are part of Operational DNA when they actually affect decisions.

A value that exists only on a poster is not Operational DNA.

A value that determines how the community decides under pressure for speed, profit, automation, or AI intensity is Operational DNA.

For example, the value of resilience becomes Operational DNA when it affects:

fallbacks,
AI lock-in rules,
Human Capability Reserve,
AI capacity allocation,
security review,
maintenance work,
disaster recovery.

Minimum requirement

Values and purpose must be connected to decisions, workflows, and AI governance in order to be a real operational part of the community.

8. Decision logic as DNA

Decision logic is one of the most valuable parts of Operational DNA.

It contains:

how the community decides,
who decides,
when escalation is required,
how trade-offs are handled,
how values are used,
how risk is handled,
how AI proposals are approved,
how change proposals are accepted or rejected.

Without decision logic, the knowledge base describes what the community knows, but not how the community thinks.

Minimum requirement

Critical decisions must be recorded as Decision Records.

Repeated decision logic should be converted into rules, checklists, workflows, or skills.

9. Workflow as DNA

A workflow becomes Operational DNA when it is critical for value creation or community operation.

Examples:

delivery workflow,
onboarding workflow,
support workflow,
incident workflow,
customer discovery workflow,
AI review workflow,
security approval workflow,
knowledge migration workflow,
Skill Evolution workflow,
AI retrospective workflow.

A workflow should be described so it is:

understandable to people,
usable by agents,
auditable,
validatable,
recoverable without a specific proprietary tool.

Minimum requirement

Critical workflows must have:

owner,
inputs,
outputs,
rules,
decision points,
AI steps,
human approval gates,
fallback,
audit trail.

10. Skills as DNA

Skills are operational capabilities of the community.

AIFC distinguishes:

human skills,
AI skills.

Human skills ensure that people can understand, perform, validate, and teach work.

AI skills ensure that agents can work repeatedly, under governance, and in line with community rules.

A skill is Operational DNA when the community loses an important capability without it.

Minimum requirement

Critical skills must not exist only in people’s heads or only in proprietary AI tools.

They must be captured in the Source of Truth or derivable from it.

11. AI governance as DNA

In an AI-first community, AI governance is part of Operational DNA.

It describes:

where the community uses AI,
why it uses AI,
which data AI may see,
which roles agents have,
what autonomy level applies,
who approves outputs,
how value is measured,
how consumption is controlled,
how AI dependency is prevented,
how fallback is handled,
how lock-in is prevented.

AI governance is not an add-on.

It is the operational structure that determines whether AI strengthens the community or makes it dependent.

Minimum requirement

Significant AI workflows must be part of the Source of Truth and must have a governance description.

12. Fallback and recovery as DNA

The ability to continue when AI, a vendor, a tool, or a key person is unavailable is part of Operational DNA.

Fallback is not a sign of distrust toward AI.

It is a sign of a mature system.

If simple routine work stops because tokens ran out, the community did not gain intelligence. It lost resilience.

Operational DNA must therefore include:

fallback for critical workflows,
Human Capability Reserve,
exportable skills,
recovery procedures,
backups,
vendor exit strategies,
tested AI-off modes.

Minimum requirement

Critical community capability must have a described recovery path.

13. Feedback and learning as DNA

A community that cannot learn degrades over time.

The feedback loop, retrospectives, Skill Evolution, and Workflow Conversion are part of Operational DNA when the community actually changes its behavior through them.

Operational DNA must include mechanisms that convert experience into system improvement.

Examples:

AI retrospective,
sprint retrospective,
incident retrospective,
change proposals,
Decision Records,
lessons learned,
skill updates,
maintenance backlog,
Workflow Conversion candidates.

Minimum requirement

Significant learning must have a path into the Source of Truth.

14. Customer and stakeholder knowledge as DNA

For companies and services, knowledge of customers, stakeholders, and served communities is a key part of Operational DNA.

It may contain:

customer needs,
pains,
jobs to be done,
decision drivers,
trust signals,
support patterns,
objections,
market signals,
relationship rules,
service principles.

This knowledge may be highly competitively sensitive.

AI may help synthesize it, but must respect the AI-NDA Boundary and data classification.

Minimum requirement

Sensitive customer and stakeholder know-how must be classified, protected, and used by AI only according to community rules.

15. Business model as DNA

In a company, Operational DNA may include the business model.

For example:

how the company earns revenue,
which segments it serves,
how it prices,
how it delivers value,
how it acquires customers,
how it maintains quality,
how it scales,
which unit economics apply,
how it uses AI capacity,
which parts of the model are replicable.

In AIFC, a business model is not an isolated spreadsheet.

It is connected to values, strategy, workflows, skills, AI governance, and the Community Interface.

Minimum requirement

If the business model is part of the knowledge base, it must have clear sensitivity classification and AI access rules.

16. Operational DNA and Company as a System

Company as a System is the application of AIFC to a company.

Operational DNA is its internal operating code.

Well-described Operational DNA allows the company to be:

understood,
audited,
improved,
managed,
secured,
scaled,
partially automated,
licensed,
replicated,
or launched in another context.

This creates a new category of value.

A company is no longer only a legal entity and group of people.

It can be described as an operable system.

Minimum requirement

Company as a System must not be a company without responsibility.

Company Operational DNA must be connected to human or community ownership of purpose, values, and critical decisions.

17. Operational DNA and Company as Product

If a company’s operating model is described well enough, it may become a product.

It may be:

licensed,
forked,
localized,
sold,
used as a template,
used to create a new company,
used as a reference implementation.

This creates a large opportunity and a high risk.

If Operational DNA leaks, it can be used to imitate or launch a similar company.

Minimum requirement

Before Operational DNA is used as a product, the community must define:

who owns it,
what may be shared,
what is restricted,
what is an operational secret,
which license applies,
who carries responsibility,
how values and purpose are protected,
how the Ghost AI Company model is prevented.

18. Operational DNA and AI access

AI agents must not have automatic access to all Operational DNA.

Access must be governed by:

purpose,
agent role,
data sensitivity,
AI-NDA Boundary,
data classification,
need-to-know principle,
auditability,
ability to revoke access.

AI can be a powerful accelerator of Operational DNA:

helping read it,
synthesize it,
clean it,
validate it,
update it,
reveal gaps,
find contradictions,
propose improvements.

But Operational DNA must not be handed to external intelligence without control.

Minimum requirement

Every AI access to Operational DNA must be approved, limited, auditable, and revocable.

19. Data classification

AIFC recommends classifying the knowledge base into at least these layers:

Public
Internal
Restricted
Operational DNA

Public

Knowledge that may be shared publicly.

For example:

public community description,
public values,
public products,
marketing communication.

Internal

Knowledge intended for community members.

For example:

internal procedures,
ordinary documentation,
onboarding,
internal guidance.

Restricted

Sensitive knowledge with limited access.

For example:

customer information,
security rules,
financial details,
internal strategy,
vendor information.

Operational DNA

Critical knowledge describing the community’s operational capability.

For example:

decision logic,
critical workflows,
competitive know-how,
AI agentic workflows,
business model,
critical skills,
fallbacks,
governance rules.

Minimum requirement

Operational DNA must have the highest common protection level inside the knowledge base.

20. Operational DNA leakage

Operational DNA leakage is not an ordinary documentation leak.

It is a capability leak.

It may happen, for example, when:

an AI tool uses internal data for training without control,
agent memory contains critical know-how outside the Source of Truth,
an employee puts a sensitive workflow into an external AI tool,
a vendor gains access to the whole operating model,
a knowledge base export is not protected,
a Ghost AI Company uses Operational DNA without values and responsibility,
a competitor obtains a structured operating model.

Minimum requirement

The community must have incident response for Operational DNA leakage.

21. Operational DNA and Human Cockpit Layer

The Human Cockpit Layer must display Operational DNA carefully.

Not every community member needs to see everything.

The Human Cockpit Layer should help people understand the system while respecting knowledge sensitivity.

It may show:

public or internal view of purpose,
relevant workflows,
personal tasks,
approved skills,
decisions available to the role,
AI rules for the work,
risks and maintenance needs,
change proposals waiting for decision.

It should not automatically show all Operational DNA to everyone.

Minimum requirement

The Human Cockpit Layer must respect data classification, role-based access, and the AI-NDA Boundary.

22. Ownership of Operational DNA

Operational DNA must have owners.

Ownership may be divided by area:

purpose owner,
values owner,
process owner,
skill owner,
security owner,
AI governance owner,
business model owner,
Community Interface owner,
knowledge owner.

Owner does not mean that the person owns the community.

It means they are responsible for correctness, update, security, and governance of the relevant part of Operational DNA.

Minimum requirement

Critical parts of Operational DNA without an owner must be marked as governance risk.

23. Lifecycle of Operational DNA

Operational DNA evolves.

It may have statuses:

draft
proposed
under_review
approved
active
deprecated
archived
restricted
compromised

The compromised status requires special attention.

It means that part of Operational DNA may have leaked, been misused, or lost confidentiality.

Minimum requirement

Critical parts of Operational DNA must have a lifecycle, review mechanism, and audit history.

24. Maintenance of Operational DNA

Operational DNA requires regular care.

Everything the community does not care for tends to degrade or create debt.

Operational DNA may accumulate:

knowledge debt,
process debt,
decision debt,
skill debt,
security debt,
AI dependency debt,
governance debt,
relationship debt between communities.

Neglected Operational DNA is more dangerous than missing documentation because it creates the illusion that the community knows how it works.

Minimum requirement

Operational DNA must have regular review and a maintenance backlog.

25. Operational DNA and AI-generated updates

AI may propose changes to Operational DNA.

For example:

workflow update,
new skill,
rule correction,
contradiction detection,
fallback proposal,
decision logic improvement,
AI-NDA Boundary change,
cleanup of outdated content.

These proposals may be highly valuable, but they must not be accepted automatically.

Minimum requirement

AI-generated changes to Operational DNA must pass human or community approval according to sensitivity and impact.

26. Operational DNA and portability

Operational DNA must be portable in a controlled mode.

Portability matters for:

backup,
disaster recovery,
vendor exit,
audit,
legal transfer,
license,
Company as Product model,
long-term preservation.

Portability must be security-governed.

Exporting Operational DNA is a highly sensitive operation.

Minimum requirement

Export of Operational DNA must be audited, authorized, and protected.

27. Operational DNA and AI lock-in

AI lock-in may emerge when part of Operational DNA moves into:

proprietary prompt workflow,
agent memory,
closed skill store,
vendor-specific automation,
model-specific behavior,
external AI knowledge layer.

Such lock-in is dangerous because the community does not lose only a tool. It loses part of its own operational capability.

Minimum requirement

Operational DNA must not depend on one AI vendor, model, agent memory, or proprietary skill store without an exit strategy.

28. Operational DNA and Ghost AI Company risk

A Ghost AI Company may emerge when someone uses Operational DNA, or part of it, to create a digital company facade without a real responsible community.

Such a company may have:

brand,
website,
content,
automated communication,
AI support,
generated offers,
agentic workflows.

But it lacks:

living purpose,
values,
responsibility,
Human Ownership,
fallback,
real ability to learn,
community governance.

Minimum requirement

Operational DNA must not be used to create an AI-first structure without an identifiable human or community owner of purpose, values, and responsibility.

29. Suggested metadata

Example metadata for an Operational DNA artefact:

operational_dna:
  id:
  title:
  type:
    - decision_logic
    - critical_workflow
    - human_skill
    - ai_skill
    - business_model
    - governance_rule
    - fallback
    - ai_workflow
    - community_interface
    - customer_knowledge
    - security_rule
  owner:
  status: draft | proposed | under_review | approved | active | deprecated | archived | restricted | compromised
  sensitivity: operational_dna
  ai_access:
    allowed: true | false
    boundary:
    allowed_agents:
    restrictions:
  human_access_roles:
  related_values:
  related_purpose:
  related_decisions:
  related_workflows:
  related_skills:
  review_cycle:
  last_reviewed:
  export_allowed: true | false
  exit_strategy_required: true | false

This structure is illustrative.

The final schema should be defined in the agent-actionable layer of the standard.

30. Anti-patterns

AIFC rejects the following anti-patterns.

30.1 Operational DNA treated as ordinary documentation

Critical know-how is stored and protected like ordinary notes.

30.2 Operational DNA without owner

Nobody is responsible for the correctness and currentness of critical know-how.

30.3 Operational DNA trapped in people

Key operational know-how exists only in the heads of individuals.

30.4 Operational DNA trapped in AI tools

Critical know-how exists only in chats, agents, or proprietary skill stores.

30.5 AI access without boundary

AI agents have access to Operational DNA without an AI-NDA Boundary and auditability.

30.6 No fallback

Operational DNA describes an AI workflow, but does not describe a non-AI recovery path.

30.7 No maintenance

Operational DNA is not maintained and gradually degrades.

30.8 No classification

The community does not distinguish ordinary knowledge, restricted knowledge, and Operational DNA.

30.9 Export without protection

Operational DNA is exported without governance, audit, or protection.

30.10 Ghost company reuse

Operational DNA is used to create a digital company without a responsible community.

31. Minimal requirements

For Operational DNA, an AIFC community must at least:

Distinguish ordinary knowledge base content from Operational DNA.
Classify Operational DNA as a critical asset.
Assign owners to critical parts of Operational DNA.
Protect Operational DNA with access rules.
Govern AI access to Operational DNA through an AI-NDA Boundary.
Maintain Operational DNA in the Source of Truth.
Ensure audit of Operational DNA changes.
Maintain lifecycle for critical artefacts.
Maintain review and maintenance mechanisms.
Give critical workflows in Operational DNA fallback.
Give critical AI workflows an exit strategy.
Require appropriate approval for AI-generated changes to Operational DNA.
Ensure the Human Cockpit Layer respects Operational DNA sensitivity.
Export Operational DNA only in a controlled and auditable way.
Treat Operational DNA leakage as a critical incident.
Prevent Operational DNA from being used to create a Ghost AI Company without a responsible community.
Connect Operational DNA to purpose, values, decisions, and the feedback loop.

32. Summary

Operational DNA is critical community capability captured in a knowledge structure.

It describes how the community actually works:

why it exists,
which values it holds,
how it decides,
how it creates value,
how it works,
how it uses AI,
how it learns,
how it protects itself,
how it recovers,
how it cooperates with other communities.

The better Operational DNA is described, the more valuable it becomes.

And the stronger protection it requires.

Operational DNA enables Company as a System.

It also creates the risk of capability leakage, AI lock-in, or a Ghost AI Company.

AIFC therefore says:

Describe how the community works.
Protect what makes it capable.
Keep humans responsible for its purpose.

Operational DNA turns knowledge into community capability.