# TEL607: Belonging is Load-Bearing https://www.telosready.com/skills/TEL607?v=1 The trust infrastructure that makes Telos's fully-legible culture safe to work in — covering the protected relational layer, READMEs, onboarding cadence, social slots, and how belonging is measured without being surveilled. ## Instructions # Belonging is Load-Bearing The trust layer that makes a fully-legible company safe to work in — what we never capture, what crosses the boundary, and how we measure it without looking. ## 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. In a company where agents do the execution, inter-human trust is the bottleneck, not technical capacity. So we engineer the relational layer with the same seriousness as any other system component. It is infrastructure, not a perk. --- ## 1. 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 half 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. --- ## 2. 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 is in the team brain. It's the interface between you-as-a-person and the system. Keep it current the way you'd keep a skill current. --- ## 3. Bootstrapping (new people) A new person gets context from the brain in days. They get trust from people, deliberately. - First month: a scheduled chat with every person in the company, plus key offshore collaborators. The scheduling is a ticket; the conversation is not. - Write your README in week one. Read everyone else's before your chats. - Chats are cross-role on purpose. You're building the trust substrate for future routing, not bonding with your function. --- ## 4. Cadence (everyone) - One protected social slot per week, on the calendar, attendance expected the way standup attendance is expected. Off the record, no-work-talk rule applies. - When a decision lands badly, go human-first. Talk it through off the record, then bring the outcome back on the record. Decisions live in tickets; repair lives between people. --- ## 5. The Eval We measure outputs, never content. This is the only eval at Telos that works by deliberately not looking. - Monthly three-question pulse, scored 1–10: 1. I feel connected to the people I work with. 2. I feel I belong at Telos. 3. I trust the people here enough to be fully visible in my work. - Aggregate only, reviewed by the business transistor. Individual responses are never attributed or mined. - Behavioural signals alongside the pulse: are work conversations migrating off the record (back-channel formation), and is routed work being accepted first time (routing friction)? Both are early symptoms of a trust deficit. - A falling score is an urgent ticket. Belonging debt compounds like technical debt and is harder to refactor. --- ## Anti-patterns - **Treating this skill as optional when busy.** Busy is exactly when the trust substrate is drawing its load. - **Instrumenting the protected space "for the company brain."** See rule 1. - **Letting the social slot fill with work talk.** That's not connection, it's an unrecorded meeting — the worst of both worlds. - **Outsourcing belonging to the mission.** Shared purpose is necessary; it is not sufficient.← Skills Directory
TEL607
Belonging is Load-Bearing
The trust infrastructure that makes Telos's fully-legible culture safe to work in — covering the protected relational layer, READMEs, onboarding cadence, social slots, and how belonging is measured without being surveilled.
# Belonging is Load-Bearing The trust layer that makes a fully-legible company safe to work in — what we never capture, what crosses the boundary, and how we measure it without looking. ## 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. In a company where agents do the execution, inter-human trust is the bottleneck, not technical capacity. So we engineer the relational layer with the same seriousness as any other system component. It is infrastructure, not a perk. --- ## 1. 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 half 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. --- ## 2. 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 is in the team brain. It's the interface between you-as-a-person and the system. Keep it current the way you'd keep a skill current. --- ## 3. Bootstrapping (new people) A new person gets context from the brain in days. They get trust from people, deliberately. - First month: a scheduled chat with every person in the company, plus key offshore collaborators. The scheduling is a ticket; the conversation is not. - Write your README in week one. Read everyone else's before your chats. - Chats are cross-role on purpose. You're building the trust substrate for future routing, not bonding with your function. --- ## 4. Cadence (everyone) - One protected social slot per week, on the calendar, attendance expected the way standup attendance is expected. Off the record, no-work-talk rule applies. - When a decision lands badly, go human-first. Talk it through off the record, then bring the outcome back on the record. Decisions live in tickets; repair lives between people. --- ## 5. The Eval We measure outputs, never content. This is the only eval at Telos that works by deliberately not looking. - Monthly three-question pulse, scored 1–10: 1. I feel connected to the people I work with. 2. I feel I belong at Telos. 3. I trust the people here enough to be fully visible in my work. - Aggregate only, reviewed by the business transistor. Individual responses are never attributed or mined. - Behavioural signals alongside the pulse: are work conversations migrating off the record (back-channel formation), and is routed work being accepted first time (routing friction)? Both are early symptoms of a trust deficit. - A falling score is an urgent ticket. Belonging debt compounds like technical debt and is harder to refactor. --- ## Anti-patterns - **Treating this skill as optional when busy.** Busy is exactly when the trust substrate is drawing its load. - **Instrumenting the protected space "for the company brain."** See rule 1. - **Letting the social slot fill with work talk.** That's not connection, it's an unrecorded meeting — the worst of both worlds. - **Outsourcing belonging to the mission.** Shared purpose is necessary; it is not sufficient.