Skip to content

Latest commit

 

History

10 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Open Framework Commons

Open Framework Commons is the small set of shared principles and boundaries for Brad Groux's Open Framework Ecosystem.

This release is scoped to exactly five independent products:

  • AI-Native Operating Framework
  • Influence Operating Framework
  • AI Dev Days
  • Relationship Operating Framework
  • Focus Operating Framework

Commons is documentation. People and agents can read it before using or changing an ecosystem product so they understand the philosophy those products share.

Commons is not a framework for accomplishing product-specific work. It is not an operating system, application, runtime, compatibility layer, certification, shared data model, or parent product.

Ecosystem at a glance

This diagram answers how five independent products can share Commons without becoming modules of it.

flowchart TB
  subgraph products["Independent products — equal provenance"]
    direction LR
    native["AI-Native<br/>Operating Framework"]
    influence["Influence<br/>Operating Framework"]
    devdays["AI Dev Days<br/>Learning community"]
    relationship["Relationship<br/>Operating Framework"]
    focus["Focus<br/>Operating Framework"]

    native ~~~ influence
    influence ~~~ devdays
    devdays ~~~ relationship
    relationship ~~~ focus
  end

  commons["Open Framework Commons<br/>Shared principles and boundaries"]

  products -. "all are in Commons scope" .-> commons
Loading

Commons supplies shared documentation beneath the products. It does not direct or rank them. Each product separately decides whether and when to adopt an exact Commons release.

Read this first

  1. Charter — purpose and authority
  2. Principles — ideas every product shares
  3. Boundaries — what stays shared and what stays local
  4. Research and review — how claims and learning remain honest
  5. Governance — how shared documentation changes
  6. Context — the vocabulary used here

How people and agents should use Commons

Read Commons for the shared philosophy, then read the selected product for the actual method, examples, and task guidance. If the two appear to conflict, pause the disputed action or representation and follow Resolving conflicts. Check the adopted Commons revision first; unrelated safe work need not stop.

Each product stands alone. A person may use one product without adopting the others.

Independent review record

Sanitized independent reviews and their disposition are published in project/reviews. Each report identifies the exact commit reviewed and its limitations. Document review does not establish adoption or real-world effectiveness.

Status

Version 2026.09.05 is the current edition. It clarifies human boundaries, conflict resolution, evidence review, and content compatibility, and starts calendar versioning. See the release notes for adoption consequences. Each product independently pins the exact Commons release it has reviewed rather than relying on a moving branch.

The five ecosystem products record their original Commons adoption in these stable release pages:

Each product owns its release target and product-local adoption evidence. Commons does not mirror downstream commit hashes or moving branch paths. For current adoption, consult the selected product’s own release history and governance. An older Commons pin remains valid until that product chooses otherwise.

Project resources

About

Shared principles and boundaries for the Open Framework Ecosystem.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

1 star

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages