# TEL607: Belonging is Load-Bearing https://www.telosready.com/skills/TEL607?v=2 The boundary between what is on the record and what is not — protecting the relational layer while keeping all substantive work fully legible. ## Instructions # Belonging is Load-Bearing The trust layer that makes a fully-legible company safe to work in — what is on the record, what is not, and why the boundary matters. ## Why this skill exists Telos runs an exposure-heavy culture: everything on the record, no private work channels, work that routes around resistance. Exposure is only tolerable where there is trust, and trust between people is built in the one place the company brain doesn't reach. The boundary between these two spaces is not optional — it is what makes the whole system credible. --- ## 1. What is on the Record All substantive work is on the record. This includes: - **Team meetings** — decisions, discussions, and outcomes are captured - **Standups** — what you're working on, what's blocking you - **Retrospectives** — reflections on how the team is working, what to change If it affects work, routing, or decisions, it belongs on the record. There are no exceptions for convenience. --- ## 2. The Boundary "Words are Data" has a complement: some words are deliberately not data. - The relational layer is off the record by design. Coffee chats, social calls, the personal dimension of any conversation — never recorded, never transcribed, never mined. This is policy, not accident. - One rule inside the protected space: **no current-work talk.** Anything about live tickets, decisions, or customers belongs on the record. This is what keeps the protected space from becoming a back-channel. - The boundary is absolute. If you find yourself wanting to capture "just a little" of it, stop. The legibility bargain holds only while the boundary is credible. --- ## 3. The README Exactly one artifact crosses the boundary, written by you, about you. - Every person maintains a README — a personal operating manual: how you work best, how to give you feedback, what you're strong at, what drains you, what you're working on improving. - Exchange READMEs before first collaboration. Two people who haven't worked together read each other's README before the first ticket, not after the first friction. - Your README lives in the team brain. It is the interface between you as a person and the system. Keep it current the way you'd keep a skill current.← Skills Directory
TEL607
Belonging is Load-Bearing
The boundary between what is on the record and what is not — protecting the relational layer while keeping all substantive work fully legible.
# Belonging is Load-Bearing The trust layer that makes a fully-legible company safe to work in — what is on the record, what is not, and why the boundary matters. ## Why this skill exists Telos runs an exposure-heavy culture: everything on the record, no private work channels, work that routes around resistance. Exposure is only tolerable where there is trust, and trust between people is built in the one place the company brain doesn't reach. The boundary between these two spaces is not optional — it is what makes the whole system credible. --- ## 1. What is on the Record All substantive work is on the record. This includes: - **Team meetings** — decisions, discussions, and outcomes are captured - **Standups** — what you're working on, what's blocking you - **Retrospectives** — reflections on how the team is working, what to change If it affects work, routing, or decisions, it belongs on the record. There are no exceptions for convenience. --- ## 2. The Boundary "Words are Data" has a complement: some words are deliberately not data. - The relational layer is off the record by design. Coffee chats, social calls, the personal dimension of any conversation — never recorded, never transcribed, never mined. This is policy, not accident. - One rule inside the protected space: **no current-work talk.** Anything about live tickets, decisions, or customers belongs on the record. This is what keeps the protected space from becoming a back-channel. - The boundary is absolute. If you find yourself wanting to capture "just a little" of it, stop. The legibility bargain holds only while the boundary is credible. --- ## 3. The README Exactly one artifact crosses the boundary, written by you, about you. - Every person maintains a README — a personal operating manual: how you work best, how to give you feedback, what you're strong at, what drains you, what you're working on improving. - Exchange READMEs before first collaboration. Two people who haven't worked together read each other's README before the first ticket, not after the first friction. - Your README lives in the team brain. It is the interface between you as a person and the system. Keep it current the way you'd keep a skill current.