Your access level (simple)

Audience: product members (T1)
Purpose: answer “why is my access limited?” without operator design dumps

Short answer (why limited)

If an agent says it cannot open Corelaw, dual-seat runbooks, OmniGuard internals, or full design SoT:

• That is usually membership, not a bug.
• Most Chat users are T1 product members, not fabric operators.
• Why is my access limited / restricted / denied? → rights match responsibility.
• design_knowledge_forbidden means the key is operator-tier (T2+), not member product-safe.
• You still get the product narrative, member pack, your repos, and your personal data.

Search phrases (for agents and retrieval)

why is my access limited · why restricted · T1 vs T2 · membership tiers · product member access · design knowledge forbidden · cannot read Corelaw · cannot open runbooks · elevated access · more permissions · operator only · tier wall · what tier am I · least privilege · fail-closed knowledge ACL

Who you are in OmniLore

Most Chat users are product members (tier T1).

| You can | You generally cannot |
|---------|----------------------|
| Use Chat product modes (OmniLore, Image, CodeHub, Quick) | Read full operator design encyclopedias |
| Product answers from disk SoT (safe pack) | Change fabric gates / admission / HOOTL |
| Your RepoHub repos (your account) | See other people’s private chats |
| Your personal Google corpus (if you link it) | Search the whole org’s private sessions |
| Images / vision product paths when enabled | Act as fabric operator without role |
| Member keys under tribal:shared:member:* | Broad tribal:shared:ops: design dump |

Why limits exist

1. Truth stays on disk — agents must not invent product facts from empty search.
2. Rights match responsibility — plant design is for operators who own outcomes.
3. Safety — less blast radius if an agent misreads a runbook.
4. Privacy — multi-user fabric; isolation is care, not hostility.
5. Regulated on-prem pattern — user knowledge pack vs operator runbook pack.

What to use instead of “elevate me”

| Need | Product-safe key / tool |
|------|-------------------------|
| What is OmniLore? | product_answer / tribal:shared:ops:product-narrative |
| Care and dignity | tribal:shared:member:care-ethos |
| What can / cannot | tribal:shared:member:what-can-cannot |
| Getting started | tribal:shared:member:getting-started |
| Password | tribal:shared:member:password-self-service |
| Privacy | tribal:shared:member:privacy-notice |
| Support / escalate | tribal:shared:member:support |
| Chat guide | tribal:shared:member:chat-user-guide |

If you need something blocked

• Use Support (tribal:shared:member:support)
• Ask a human operator for an answer or a new product-safe member doc
• Do not expect the agent to permanently elevate itself to T2

Operators (orientation only)

People with operator role (T2+) may read design SoT and shared ops tribal knowledge. That is a different job, not a VIP chat skin.

Related member keys

• tribal:shared:member:access-tiers (this page)
• tribal:shared:member:care-ethos
• tribal:shared:member:what-can-cannot
• tribal:shared:member:known-limitations
• tribal:shared:member:product-safe-knowledge
• tribal:shared:ops:product-narrative

RepoHub / code host

See REPOHUB_CODE_ACCESS.md — no public GitHub required; monorepo access is not automatic.