Welcome to Telos Discussions!

[danielmiessler]

👋 Welcome to TELOS Discussions!

TELOS is a framework for creating Deep Context about things that matter to humans—from individuals to organizations to entire programs.

This is a place where our community comes together to:

• Share use cases - How are you using TELOS? What entities are you documenting? Show us your TELOS Context Files
  (TCFs)!
• Ask questions - Stuck on structuring your mission, goals, or strategies? Need help with the framework? Ask away.
• Propose improvements - Ideas for enhancing the TELOS framework? Suggestions for new sections or approaches? We
  want to hear them.
• Connect with others - Find people using TELOS for similar purposes, whether that's organizational strategy,
  personal development, or program management.
• Collaborate - Share patterns, templates, and lessons learned from implementing TELOS in the real world.

Whether you're documenting a security program, articulating your company's mission, or structuring your personal goals, you're in the right place.

Let's build a community that helps entities of all sizes articulate their purpose and pursue it with clarity. 💪

[saranathrajaram11]

It's great what did you use to make this like any programming language

[basharder]

this is fantastic - i loved your idea of "company graphs" from a recent video you did where you talked about a group of 22y/o's walking into an office building and interviewing everyone about what they do to put together a full company graph and thought that could also be automated.

i put together an HTML questionnaire that is department agnostic in order to capture as many job functions as i could with a single artifact.

this could also be tailored into a "help be build my Telos doc" style where you can visually see a map of yourself in the same way you vision this on a company level. this would also vectorize it directly for the "how can my services i provide help me" that can be included into an AI assistant marketplace as you describe it.

i'm working on the collection suite for this that could connect and intertwine multiple different user submissions into a full network but that is still in the works. after that would be an MCP call to the individual questions using Claude's new multiple choice questioning tool that could actually deliver the different sections of my questionnaire and put the doc together without a dedicated UI - or better yet, have your personal AI fill it out for us
questionnaire.html

[anthonypica]

Thank you for creating Telos and sharing it. I've got an amateur question about efficiency and interoperability with PAI. In this repo, there is one file with multiple sections for History, Goals, Narratives, etc. But in my implementation with PAI, I ended up with a distinct file for each i.e. GOALS.md and CHALLENGES.md. Is that okay, or is it better to have one single file?

[basharder]

What is the practical use of having multiple? Is it so they can be used independantly? I think of this as a brain.md etc that is my identity in a single document that you COULD drop into any model/system and it already knows what you are about instead of multiple versions leading to the same conclusion

[anthonypica]

Good news, I discovered that having multiple files is recommended via PAI. https://github.com/danielmiessler/Personal_AI_Infrastructure/blob/main/Releases/v4.0.3/.claude/PAI/USER/TELOS/README.md