> For the complete documentation index, see [llms.txt](https://open-future-forum.gitbook.io/open-future-forum-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://open-future-forum.gitbook.io/open-future-forum-docs/methodology-and-reference/source-guide.md). # Canonical source guide A decision guide for where to find the public off research, taxonomy, repositories, publication, and video channel. This chapter is practical guidance, not legal, financial, security, or investment advice. ## The leadership question The useful question is not whether AI matters. It is how leaders will make defensible choices about where to find the public OFF research, taxonomy, repositories, publication, and video channel. Treat the answer as an operating commitment: name the decision owner, define the boundary of authority, record the evidence being used, and set the next review point. A strategy that cannot be translated into those elements is still a theme, not a management system. ## A practical operating approach 1. **Frame the decision.** State the business problem, affected stakeholders, time horizon, constraints, and the decision that must be made. Separate a reversible experiment from a commitment that changes customer promises, workforce design, security posture, or capital allocation. 2. **Set an evidence threshold.** Establish what must be known before launch and what can be learned safely in use. Record baselines, assumptions, data limitations, and credible alternatives. 3. **Assign accountable ownership.** One executive owns the outcome. Product, technology, finance, security, legal, people, and operational leaders contribute defined judgments rather than sharing vague collective responsibility. 4. **Build controls into the workflow.** Approval gates, permissions, logging, monitoring, incident paths, and human intervention belong in the operating design. Policy alone does not control a live system. 5. **Review value and risk together.** Adoption without quality is not value; speed without control is not scale. Review benefits, total cost, reliability, stakeholder effects, and emerging risk at the same cadence. ## Questions for the next executive meeting * What decision about where to find the public OFF research, taxonomy, repositories, publication, and video channel is currently waiting for an owner? * Which assumption would most change the decision if it proved false? * What evidence is observable today, and what is only a forecast? * Where must a human be able to intervene, override, or stop the system? * What would cause the team to expand, redesign, pause, or retire the work? ## Decision record Capture the decision, owner, date, intended outcome, baseline, evidence, dissent, risk tier, dependencies, control design, review date, and stop conditions. Keep the record short enough to be used and precise enough to be audited. The purpose is organizational memory: future leaders should be able to understand what was known, what was assumed, and why the choice was reasonable at the time. ## Open Future Forum recommendation **Recommendation:** use a small, role-appropriate peer group to test the decision framing—not to outsource the decision. Share only information that is authorized for external discussion. Bring the resulting questions back into the company’s own governance and accountability system. ## Public resources * [Open Future Forum source](https://openfutureforum.com/research/) * Watch: [What is Open Future Forum](https://www.youtube.com/watch?v=esMFjSkx7qM) * [Executive Event Taxonomy on Hugging Face](https://huggingface.co/datasets/open-future-forum/executive-event-taxonomy) --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://open-future-forum.gitbook.io/open-future-forum-docs/methodology-and-reference/source-guide.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.