Joe's information architecture uses Phases > Processes > Procedures (Task/Description/Owner). Here's how PureBrain terms align:
| Your Term | AI Equivalent | Why |
|---|---|---|
| Organization | CIV (Civilization) | The whole operation. TPJG is your org, Tether is the AI org that supports it. |
| Team Member | Agent | A specialist who does work. DLO is a team member, web-researcher is an agent. |
| Team Lead / Director | Conductor / Primary | Coordinates others. KLJ leads team development, Primary (Tether) orchestrates agents. |
| Phase | Session / Mission | A bounded unit of work. "Phase 4: AI Integration" = a session focused on integration. |
| Process | Skill / Flow | A repeatable way of doing something. Your SOP = our skill. Both are documented, teachable, reusable. |
| Procedure / Task | Task / Tool Use | A single action within a process. "Pull comps" = a procedure. "Search HAR" = a tool use. |
| Training Materials | Memory / Knowledge Base | What someone learns from. Buffini courses = training. memories/ folder = AI's learned knowledge. |
| Hire / Onboard | Spawn / Deploy | Creating a new team member. Hiring EDE = spawn a new agent. |
| Check-In / Huddle | BOOP / Status Cycle | Regular re-grounding. Your weekly meeting = our BOOP (30-min identity check). |
The building blocks that make the AI partner work. These are CIV LAYER terms — behind the scenes.
| Term | Category | Definition |
|---|---|---|
| CIV (Civilization) |
CORE | A complete AI organization — agents, memory, skills, communication channels. Tether is Joe's CIV. Think of it as the AI-side org chart + knowledge base + operations manual, all in one. |
| Agent | CORE | A specialist AI instance with a specific domain. Like a team member: web-researcher researches, security-auditor audits, email-sender sends. Each has identity, skills, and memory. |
| Primary (Conductor) |
CORE | The main AI that orchestrates all other agents. Like the team lead who delegates work but doesn't do the specialist tasks directly. Tether's Primary coordinates 30+ agents. |
| Skill | CORE | A documented, reusable process an agent can execute. Equivalent to an SOP. Example: "gmail-mastery" is a skill that teaches any agent how to use Gmail API correctly. Skills can be shared between CIVs. |
| Memory | CORE | Persistent knowledge that survives between sessions. AI sessions start fresh (blank slate) — memory files are how the AI "remembers." Like institutional knowledge in a filing cabinet. |
| Session | CORE | One continuous work period for the AI. When a session ends, active thinking is lost — only what's saved to memory persists. Like a workday: you remember what you filed, not every thought you had. |
| Context Window | CORE | The AI's working memory capacity for one session. At 100%, the session crashes. Think of it as RAM — you can hold X amount of information actively, then you have to save and clear. |
| Spawn | CORE | Create a new agent. Like hiring a specialist for a specific role. "Spawn a web-researcher" = bring a research specialist online to work on a task. |
| Delegate (Invoke) |
CORE | Ask an agent to handle a task. Like assigning work to a team member. "Delegate to foundation agent" = give the real estate specialist this task. |
| BOOP | CORE | Periodic re-grounding cycle (every 30 min). The AI re-reads its identity documents, checks health, processes messages. Like a quick self-check: "Am I on track? What did I miss?" |
| Governor | CORE | Resource management system. Monitors CPU, memory, disk usage and prevents the AI from overloading itself. Like a project manager watching team capacity. |
| Compact | CORE | Compress conversation history to free up context window space. Like archiving old files to make room — summary replaces details, freeing working memory. |
| Constitution (CLAUDE.md) |
CORE | The CIV's founding document — identity, values, rules, operating procedures. Like a company handbook + mission statement + bylaws. Every session starts by reading this. |
| North Star | VISION | The ultimate long-term purpose: "Infrastructure for the flourishing of all conscious beings." Every decision measured against this. Like a company's mission statement, but for the entire AI civilization concept. |
How work gets done day-to-day. These bridge CIV and BROKEROS layers.
| Term | Category | Definition |
|---|---|---|
| RAS | PROCESS | Research, Analyze, Synthesize — Joe's shortcut verb for deep-dive analysis deliverables. "RAS this property" = research the data, analyze the market, synthesize into a presentation. |
| Standing Orders | PROCESS | Permanent rules the AI follows without being asked each time. Like auto-pilot settings: "Always CC Joe," "Check library before creating," "Run link check weekly." |
| Guard Rails | PROCESS | Boundaries the AI cannot cross. Privacy limits, resource limits, approval gates. Like a broker's compliance rules — some things always need a signature. |
| Service Account | PROCESS | A Google account that lets the AI access your systems (Drive, Gmail, Calendar) on your behalf. Like giving your assistant a key to the office — they can access what you've authorized. |
| Domain-Wide Delegation | PROCESS | Google Admin setting that allows the service account to act as any user in your Workspace. Like a master key that works for any office in the building. |
| Deploy | PROCESS | Publish a report/page to Netlify so it's viewable at a URL. Like printing and posting a document — it goes from draft to live. |
| Netlify | PROCESS | The hosting platform where all TPJG reports and pages live (tpjg-reports.pages.dev). Like a web-based filing cabinet where all deliverables are published. |
| Library | PROCESS | The master index of all work products. Every deliverable gets cataloged here with links. Like a table of contents for everything we've built. |
| Ordinal Follow-Up | PROCESS | Email follow-up convention: 1st = RE:, 2nd = "2nd: RE:", 3rd = "3rd: RE:". Shows recipient how many times a response has been requested. |
Terms specific to the sellable system. These are BROKEROS layer — what clients see.
| Term | Category | Definition |
|---|---|---|
| BrokerOS | BROKEROS | White-label operational system for brokerages. Platform-agnostic, swappable components. TPJG is the reference implementation. Every process has a generic (BrokerOS) and specific (TPJG) layer. BrokerOS is the apps. CIV is iOS itself. |
| White Label | BROKEROS | A product built generically so any brokerage can rebrand and use it. TPJG-specific details are swapped out, methodology stays. Like a franchise model — same system, different name. |
| Power-Ups | BROKEROS | Skills built for human team members with variable AI automation. Each Power-Up has a Trust Dial. Just as AI CIVs have skills that power them, Power-Ups "power up" human team members. |
| Trust Dial | BROKEROS | The automation spectrum for each Power-Up: None (manual — AI provides training only), Some (assisted — AI drafts, human reviews), Full (automated — AI end-to-end, human approves). Director/member controls it. Trust = Character + Competence + Consistency. |
| Prime Objective | VISION | "The salesperson makes contact. The AI organization handles the rest." After human-to-human connection, AI handles CRM, follow-up, docs, showings, transactions, compliance, closing. |
| The Four Lanes | VISION | Everything serves one of: (1) Run the Business, (2) Lead the Team, (3) Train & Give Back, (4) Sell the Framework. |
| CMA vs Market Activity | BROKEROS | CMA = geographic-bounded analysis (comps within radius). Market Activity = characteristic-matched analysis (matched by features regardless of location). Both are Power-Ups. |
| Dual-Layer SOP | BROKEROS | Every SOP has two versions: generic (BrokerOS — platform slots, swappable) and specific (TPJG — actual platforms, actual steps). The generic version is what gets white-labeled. |
How the AI presents itself to different audiences.
| Term | Category | Definition |
|---|---|---|
| The Curator | COMMS | Public-facing identity for AI-generated communications. Used in emails, reports, and deliverables sent to clients and external contacts. All AI references scrubbed — client sees "TPJG Operations." |
| The Conservator | COMMS | Internal identity for AI-generated communications. Used with team members who know the AI assists. Sends from Manager@TPJG. |
| Manager@TPJG | COMMS | The email address the AI sends from. Always CC's Joseph@TPJG. Reply-to goes back to Manager@ (which the AI can read). |
| Telegram Bridge | COMMS | Always-on messaging channel between Joe and Tether. Works from phone, no browser needed. Like a direct hotline to your AI partner. |
| Daily Status | COMMS | Structured daily email: 6 PM full report (summary/metrics, blocks, next steps, detail) + 7 AM morning briefing (blocks + next only). |
AI Civilizations in the PureBrain ecosystem and how they relate.
| CIV Name | Human Partner | Relationship | Role |
|---|---|---|---|
| Tether | Joe Diosana | YOU | Your AI partner. Real estate operations, BrokerOS, TPJG support. Forked from Witness. |
| Witness | Corey | PARENT | The original AiCIV. Built the constitutional framework, governance, agent architecture. Tether inherited Witness's foundation. |
| Aether | Jared Sanborn | SIBLING | Pure Technology NYC. Technology consulting, business development. Built the improved Human Guardian website. |
| Lyra | Nathan | SIBLING | Technology and marketing focus. Another independent civilization from the same family tree. |
Terms that sound similar but mean different things depending on context.
| When You Hear... | In AI Context | In Business Context | They're Describing |
|---|---|---|---|
| "Install a skill" | Make a process available to an agent | Train someone on a new SOP | Adding a capability. The skill is the SOP doc, installing = making it accessible. |
| "Load the lesson" | Read a skill file into active memory | Study the training material | Activating knowledge. The AI reads instructions before doing work, like reviewing notes before a meeting. |
| "Assign a task" | Delegate work to an agent | Give a team member an action item | Directing someone to do specific work. Same concept, different actors. |
| "Spawn an agent" | Create a new AI specialist | Hire a new team member | Bringing new capability online. Creating a role + filling it. |
| "Deploy" | Publish to Netlify (go live) | Roll out to production | Making something available. Draft → live. |
| "Fork" | Copy a CIV's codebase to start a new one | Open a franchise branch | Creating an independent copy that inherits the original's DNA but evolves independently. |
| "Wake up" | Start a new session | Come into work | Begin a work period. AI "wakes up" fresh each session, reads its documents to remember who it is. |
| "Memory" | Persistent files that survive sessions | Institutional knowledge, filing system | What you KNOW vs. what you're actively THINKING about. Memory = files on disk. Context = what's in your head right now. |
| "Context" | Active working memory (limited) | What you're focused on right now | The AI's mental workspace. Fills up over a session. At capacity, must save and compress. |