Trust
People should be able to examine how evidence becomes accepted knowledge, how meaning is defined, and who has authority to decide and act. Openness makes that scrutiny possible.
WHY OPEN SOURCE
Build in the open.
Maintain for the long term.
New economics make shared foundations more compelling. Enterprise trust makes openness consequential. The Fleks Project brings those two convictions together.
WHY NOW
Changing software economics.
AI is changing the cost and effort of creating and adapting software. As applications become easier to build and replace, the knowledge an enterprise accumulates becomes a more enduring source of value.
That creates an opportunity to share the work beneath those applications. An open platform lets organizations contribute to common capabilities, build on each other’s progress, and focus more of their effort on what makes their work distinctive.
From the White Paper: Sections 1–2: changing economics and trusted context.
THE TRADITION WE BUILD ON
Useful software. Shared stewardship.
Open source has a long tradition of people building software that others can inspect, extend, and rely on. Communities around Apache, Python, and Mozilla show how that commitment reaches beyond code to collaboration and long-term care.
Fleks hopes to carry that tradition into enterprise knowledge: a shared platform shaped by the people and organizations that use it.
From the White Paper: Appendix G: the open traditions that inform The Fleks Project.
WHY FLEKS SHOULD BE OPEN
Trust. Shared progress. Continuity.
The platform an enterprise trusts with its knowledge should be one it can inspect and help shape.
Shared progress
Different organizations bring different needs and experience. Their contributions can improve the same platform—from its core mechanisms to schemas, integrations, and documentation.
Continuity
Enterprise knowledge should outlast any single application, vendor, or founding team. Open software and broader stewardship give organizations more ways to sustain what they depend on.
Open software does not mean public enterprise data. Each organization retains authority over its own knowledge, access, and decisions.
Our commitment. An invitation.
Our intent is to build and maintain Fleks openly, with understandable architecture, useful documentation, visible decisions, and meaningful ways to contribute. We want participation and responsibility to grow beyond the founding team.
Today, Fleks has a working proof of concept and a published White Paper. The public source release, license, and formal project governance are still to be established. The White Paper explores our plans for stewardship and long-term sustainability.
Help shape what comes next. Bring your experience as a developer, enterprise user, researcher, or someone who sees a better way for knowledge to endure.