GET INVOLVED
Help build the trusted knowledge plane for the enterprise. Bring your experience, your questions, and the willingness to shape an open foundation together.
Tell us about your workflow using fictional or anonymized examples. Please don’t send confidential business information, sensitive personal information, passwords, or API keys.
Examine the architecture, build integrations, improve the experience, strengthen documentation, and help make a meaningful first installation accessible to others.
Bring real workflows, missing concepts, difficult ambiguities, and the practical burden of review. Help test whether the foundation supports the distinctions that matter in your work.
Challenge the assumptions. Investigate stability, provenance, authority, and semantic change. Design evaluations that can distinguish architectural promise from demonstrated benefit.
Help shape contribution practices, maintainer responsibility, licensing decisions, sustainability, and continuity. Experience building and sustaining open projects is especially valuable.
PROPOSED WORKING GROUPS
A trusted knowledge plane needs people who can shape its foundations, challenge its assumptions, and make it useful in everyday work. These areas offer concrete places to begin.
We are seeking contributors and founding leads for these proposed groups. Their scope and ways of working will take shape with participants; they are invitations to organize the work.
Establish the organizational and legal footing for a sustainable open source project, with transparent decisions and accountable stewardship.
Ways to contribute: Help shape licensing, the public source release, contribution channels, organizational and funding arrangements, and maintainer roles. Propose decision procedures, conflict resolution, and succession practices that keep project stewardship distinct from enterprise authority over private knowledge.
Define how enterprise concepts and relationships can evolve while accepted meaning remains traceable.
Ways to contribute: Develop reusable plain-language schemas, propose review and adoption workflows, and explore how earlier activity can reveal missing concepts.
Turn activity into proposed facts and relationships through schema-guided semantic processing.
Ways to contribute: Improve ambiguity handling and evidence-linked proposals across domains. Explore learning from reviewed outcomes while keeping business meaning in schema and acceptance under explicit authority.
Preserve accepted context and the evidence, definitions, and decisions that explain it.
Ways to contribute: Strengthen durable records, relationship history, correction semantics, and provenance inspection. Help make accumulated experience useful without rewriting earlier knowledge.
Develop acceptance within explicitly granted authority, informed by evidence, risk, and tolerance.
Ways to contribute: Design policy review, evaluation, and escalation to human judgment. Use historical outcomes to assess policies and calibrate confidence while keeping acceptance distinct from permission to act.
Protect enterprise knowledge while enabling appropriate participation by people, applications, and agents.
Ways to contribute: Develop threat models, access boundaries, privacy controls, and auditable permission checks. Examine how shared context respects organizational and information boundaries.
Keep the knowledge plane responsive and economical as activity, history, and participation grow.
Ways to contribute: Measure end-to-end latency, model cost, throughput, and retrieval behavior. Investigate improvements that preserve semantic completeness, provenance, and governance.
Make connected context understandable and consequential decisions clear.
Ways to contribute: Shape FleksScenes, evidence review, ambiguity resolution, and acceptance flows. Bring accessibility expertise, interaction design, and real workflows to evaluate the experience.
Help applications, agents, and contributors build on the shared foundation.
Ways to contribute: Develop APIs, connectors, SDKs, installation guidance, and examples. Make it clear how integrations contribute evidence, retrieve authorized context, and respect acceptance and action boundaries.
Establish credible, reproducible evidence of quality, reliability, and architectural behavior.
Ways to contribute: Contribute representative scenarios and human review rubrics. Evaluate interpretation, ambiguity, persistence, and authority boundaries, and publish findings with their practical limits.
Which part of your organization’s understanding is hardest to preserve as its tools change? What would a shared knowledge plane need to make visible before you trusted it? Which architectural property would you want to test first?
Useful participation can begin with a carefully described scenario, a critique of the White Paper, or a proposal for a reproducible evaluation. Shared progress does not require publishing private enterprise knowledge.
Tell us which working group interests you, what experience or perspective you bring, and a concrete piece of work you would like to help with. You can contribute, help form and lead a group, or propose an area we have missed.
A well-described use case, a documentation improvement, or a thoughtful evaluation can be a valuable place to start.
Tell us about your workflow using fictional or anonymized examples. Please don’t send confidential business information, sensitive personal information, passwords, or API keys.
bcalvanese@fleksapp.com
The Fleks Project is an independent software project led by Brian Calvanese. Its first distributable is currently in development.
The project’s proposed direction is to broaden maintainer responsibility as sustained participation grows. Contributors should be able to understand who makes decisions, how to challenge them, and how to earn a role in stewardship.
Useful software, honest evidence, and transparent decisions are how The Fleks Project intends to earn that participation.
From the White Paper: Sections 7.3–7.4: participation and stewardship.