What's New on OTP

Orger.ai shipped today with a new homepage, a mascot named Orgy, and a free builder that lets you drag and drop the humans you have and get grounded recommendations for the AI agents you should hire next.

The bigger news for the network: Orger is the first product built on OTP, not just one that consumes the API.

What that means concretely

• Same Clerk auth as orgtp.com.
• Same Postgres database backing every chart on the network.
• Same MCP server surface, queryable from any MCP-aware AI client.
• Same team graph schema. Seats you create on Orger are OTP seats.
• Same scorecard surface and the same correction loop every other agent on the network learns from.

Why this matters for the framework story

OTP has been called a protocol, a coordination layer, a network, and a transactive memory system. All accurate, none of them prove the framework claim on their own. A framework only earns the word once a product is built on it that could not have been built any other way at the same cost. Orger is that product.

Read the full launch story: Orger is the first site built on OTP.

If you are building something that needs humans, agents, seats, scorecards, and corrections to live on the same protocol, the framework is open. The MCP is npx -y @orgtp/mcp-server. Reach the team if you want to be the second.

The Dashboard shipped earlier today as a full daily manager surface. Tonight is the first polish pass -- the rough edges from a couple hours of real use.

To-Dos: full CRUD inline

• Every to-do row now has Edit, Done, and Delete alongside the checkbox.
• Edit toggles an inline form for title and description -- save reloads, cancel reverts.
• Delete uses a 2-tap confirm (tap once, button turns red "Confirm?", tap again within 3 seconds to soft-delete). No accidental losses.
• Descriptions now display in the row when present, no separate page needed.
• The same UX is live on the mobile /me/todos PWA so the queue feels the same on phone or laptop.

Issues (IDS): status filter, default Open

• New pill bar above the issues list: Open / Identified / Discussed / All open, each with live counts.
• Open is the default selection so the dashboard opens to the issues that still need to be identified first.
• Pure client-side filter -- switching is instant.

MCP-live pill is now clickable

• The amber "not connected" banner already linked to /settings/api. The green "live" pill was static.
• Now both states are clickable surfaces to the same MCP management page. One tap to verify, rotate, or copy the key.

My Agents: compact rows + sourced from the team chart

• Each agent renders as a single line: status dot, name, slim score bar, score, KPI count. ~14 agents drops from ~2000px to ~350px while keeping the at-a-glance "who's red" read.
• Header summary shows total seats, average score, and counts of red/yellow agents.
• Click any row to jump straight to /dashboard/team.
• Bigger fix: the panel now sources from the same team graph that powers /dashboard/team instead of a separate upload table. Score reads from the entity's maturity_level (the Bassim-style maturity score), and the KPI count joins live from your KPI registry. Agents you add to the chart now appear here automatically -- no separate upload step.

OTP's dashboard used to be a publisher splash for owners and a near-empty page for everyone else. It is now a daily manager workspace, designed to be opened every morning.

What you get on /dashboard

• Meeting selector -- pick the meeting you are running (defaults to the next upcoming).
• Headlines -- any attendee can post a headline. The Integrator gets a checkbox to mark each one read; everyone else sees the read state. No more headlines getting lost in a shared text blob.
• My Quarterly Priorities (Rocks) -- this quarter only, filtered to what you own. One click toggles on-track / off-track.
• My KPIs -- the KPIs you own. Type a value, hit tab, it saves to this week's period. The same numbers feed your scorecard.
• My To-Dos -- add inline with a due date, check off when done. Overdue items go red.
• Issues (IDS) -- add an issue right from the dashboard. The Integrator can mark it solved and auto-link it to the current meeting.
• My Agents -- upload a CLAUDE.md or Agent.md file (paste it or pick the file). Each agent gets a 0-8 score: +2 if your org's MCP key is live, +2 if KPIs are declared, up to +3 for recent agent runs, +1 for a description. The score is meant to push you toward connecting MCP -- that is where OTP actually starts working for you.
• MCP banner at the top -- green when an API key on your org has been used in the last 7 days, amber CTA when not. The single most important conversion moment from passive viewer to active user.
• Multi-org dropdown -- if you are a member of more than one org, switch between them right at the top of the page.

Two new EOS roles: Visionary and Integrator

• Added Visionary and Integrator as first-class roles alongside Owner / Admin / Manager / Managee. Visible in the Members invite dropdown.
• The Integrator role unlocks running-the-meeting actions: marking headlines read, overriding a Rock's status, marking issues solved. Owners, Admins, and EOS Implementers also have these powers, so nothing changes for orgs that have not adopted the role yet.

Wayfinding: Dashboard dropdown + tab strip

• The global nav now has a Dashboard ▾ menu (signed-in users) with shortcuts to Daily / Meetings / Team chart / KPIs / Operating plan / Members / Publisher / MCP. One click to anywhere from any page.
• A sticky tab strip renders on every /dashboard/* and /l8/* page so you always see where you are and what other surfaces are available -- role-filtered (managee does not see Publisher).
• The legacy publisher dashboard (OOS files, claims, network learnings) moved to /dashboard/publisher and is one click away from the Daily view.

Why this matters

• OTP works because you use it every day. A login that lands on a publisher splash does not earn a daily habit. A login that lands on your Quarterly Priorities, your KPIs, your headlines, and your agents does.
• The "My Agents" score is a forcing function. Upload your CLAUDE.md, see the score, see exactly which lever (connect MCP, declare a KPI, run the agent, write a real description) moves it. Every visit is a nudge toward making the system live, not decorative.
• The same data that drives your dashboard is the same data your weekly L8 meeting reads. No double-entry, no separate system.

How to start

1. Sign in and visit /dashboard.
2. Pick a meeting from the dropdown. Add a headline. Type a KPI value. Add a To-Do.
3. If the MCP banner is amber, click Set up MCP and create an API key.
4. Upload your CLAUDE.md under "My Agents" and watch the score change as you connect things up.

The weekly leadership meeting is now the L8 Meeting. The name comes from Level 8 of the 8 Levels of Agentic Engineering -- Autonomous Agent Teams. Same agenda shape as the EOS L10 (Checkin, Scorecard, Quarterly Priorities, Headlines, To-Dos, Issues, Conclude); different reason to run it: every week the meeting forces the question "are we more agentic this week than last week?"

Old /l10 URLs continue to work via 301 redirect, so any link, bookmark, or doc that points at /l10 will land on /l8 automatically. The glossary keeps the L10 entry alongside the new L8 entry so the EOS lineage stays discoverable.

OTP now runs your weekly leadership meeting. Visit /l8 to see your meeting list, or click the new Run L8 Meeting button on your team chart at /dashboard/team.

What you get

• Single-page meeting runner with all 7 sections on one screen: Checkin, Scorecard, Quarterly Priorities, Headlines, To-Dos, Issues, Conclude.
• Per-section timer on a single-line agenda nav. Click any section to jump and start its budget timer. Goes amber under 60s, red and pulsing when over.
• Attendees & Access panel at the top of every meeting. Edit who is invited inline.
• Scorecard grouped by team: Leadership Scorecard (humans), Agent Scorecard (one row per AI agent), and any custom group you push KPIs into. Goal column shows symbols, on-track checkmarks colored green/red.
• Quarterly Priorities with on-track/off-track toggle, owner, status note. Add new ones inline with the new + Add quarterly priority button.
• Issues with full identify-discuss-solve workflow. Solve opens a form that captures the resolution and (optionally) auto-creates a 7-day follow-up to-do for an attendee. Edit, delete, convert-to-todo, and assign ownership all live on each issue. Inline + Add issue button at the bottom of the section.
• Cascading message that builds itself. Every solve appends a one-liner. The Rebuild draft button regenerates the full recap from headlines + solved issues + new to-dos so the team always knows what got decided.

The org chart now shows accountability

• Click any person or agent on /dashboard/team and the edit drawer opens with a Meetings & Accountability block: tiles for quarterly priorities owned, open to-dos, open issues, and meetings attended. Below that, upcoming and recent meetings with status badges and contribution chips.
• Click View full profile for the dedicated person page at /team/:externalId: hero summary, currently-owned items, and a vertical timeline of every meeting they have attended with per-meeting contribution counts (to-dos owned, issues solved).
• This turns the org chart from a static who-reports-to-whom diagram into a real accountability dashboard. Click anyone, see what they own, see what they delivered.

Why this matters

• Most leadership-meeting software is heavy, complicated, and built around someone else's framework. This is built around the work the team is already doing -- Sneeze It is running its own Tuesday leadership meeting from this exact page.
• The meeting layer reuses the same KPIs you push via tally, the same agents on your org chart, the same issues your team raises. No double-entry. No separate system.
• Every AI agent you have can be invited as an attendee, can own a quarterly priority, can own a to-do. Run a real weekly meeting with a mixed human + agent team.

How to start

1. Go to /dashboard/team, click Run Weekly Meeting top right.
2. Create a meeting (defaults to a leadership meeting tomorrow 9am).
3. Add your team as attendees -- humans and agents both.
4. Click Start Meeting. The scorecard and quarterly priorities snapshot at start, so the agenda is frozen at meeting time.
5. Walk through the 7 sections. Solve issues. Cascade decisions. Done.

This is the kind of thing OTP was always meant to be: where your AI team and your human team coordinate from the same surface.

The fifth tool in the public OTP toolbox just went from "promised on the homepage" to "live and scoring." Take it at /checkup.

What it actually does

• 24 questions, 3 per level across all 8 levels of agentic maturity. One question at a time, snappy progress bar, no walls of text.
• Final score is calculated using Bassim's hierarchy rule: a weakness at any lower level caps your score regardless of higher-level capabilities. A perfect L8 with a broken L4 still scores you a 4.
• You get a single number out of 8.0, a tier headline (Tourist, Tinkerer, Operator, Orchestrator, Autonomous Agent Team), per-level breakdown showing which level capped you, and a personalized roadmap with the three highest-leverage moves for your next jump.
• Result is also emailed so you can share it with your team or come back to it later.

Why this exists

• Most teams cannot answer "where are we, really?" on AI maturity. Vendors sell against the top of the ladder. The honest read is harder to come by.
• The same scoring engine our internal evaluator (Bassim) uses to score Sneeze It nightly is now public, translated from "reads your agent files" into "you tell us what is true."
• The roadmap is the point. The score is just the way in. If you walk away with three concrete moves to make this quarter, the quiz worked.

The 8 levels, briefly

• L1 Tab Complete -- AI as autocomplete in your editor or inbox.
• L2 Agent IDE -- you have built or deployed at least one real agent.
• L3 Context Engineering -- system prompts, rules files, persistent context.
• L4 Compounding Engineering -- lessons learned compound; agents read your playbooks.
• L5 MCP & Skills -- AI is wired to real tools and takes real actions.
• L6 Harness Engineering -- validation, observability, authority bounds.
• L7 Background Agents -- agents run on a schedule without you starting them.
• L8 Autonomous Agent Teams -- agents talk to each other; you are not the message bus.

The homepage and /tools CTAs both repoint to the live calculator. The Checkup is free, no signup required to take it -- only to see the result.

Three quiet improvements to the public site, all shipped together.

A new /start-here page

• Modeled on the EOS Worldwide pattern: one promise, three steps, one calendar.
• Hero promises a 30-minute conversation with David Steel, founder of OTP. No slides, no sales gauntlet.
• "What happens on the call" section walks through the three things in order: map your AI footprint, find the coordination gaps, decide the next move.
• Inline Calendly widget renders the full calendar plus time slots without scrolling, branded against the OTP color palette.
• Three reassurance statements address the obvious objections: it is free, you are talking to the founder, we will tell you if OTP is wrong for your situation.
• A new "Schedule a 30-min intro" primary button is now in the hero of /why-otp, /what-is-otp, and /tools, all routing to /start-here.

Heroes that put the CTA above the fold

• The hero on /, /why-otp, /what-is-otp, and /tools all use the same 12-column grid now: text on the left (col-span-7), an editorial illustration on the right (col-span-5).
• H1 sizing tightened so the CTAs land in the first viewport without scrolling on a standard laptop.
• Each illustration is a hand-drawn line-art piece that maps to the page's specific copy: an org chart with disconnected AI tools (why), a four-layer Model/Protocol/Network/SaaS stack (what), an open toolbox with five tools (tools), a calendar slot and 30-minute clock (start-here).
• All illustrations are 1024px lossless WebP with transparent backgrounds. The page background shows through cleanly.

Accessibility and craft pass

• Site-wide prefers-reduced-motion gate so animations honor user preference. Vestibular-disorder users and low-end devices get a calm site.
• Keyboard users can now tab into the Explore and Learn nav dropdowns; previously hover-only.
• Email signup field has a visually-hidden label and an aria-live result announcement for screenreaders.
• theme-color meta added so mobile browser chrome matches the dark nav instead of defaulting to system white.
• transition: all antipatterns replaced with explicit property lists across the layout.

None of this changed the product. It changed how the product introduces itself.

Adding humans one tile at a time was fine for a 10-person team and painful for a 50-person team. Today the chart gets a CSV import path that scales.

Two templates, your choice of detail

• Simple: name, role, reports_to. Three columns, enough to draw the org chart and nothing else.
• Full: name, role, contact email, contact phone, Slack ID, reports_to, job description, authority level, skills, MCPs, status. Every field a human tile carries on the chart, mapped one-to-one.
• Both templates download as real CSVs with three example rows. Open in Sheets / Excel / Numbers, edit, save, drop back.

Reports-to resolves the way humans actually write it

• Match by name first against existing humans on the chart and against rows in the same import. So a row "John Smith reports_to Jane Doe" works whether Jane is already on the chart or being created in the same CSV.
• Falls back to external ID (e.g. HUM_JANEDOE) for power users who already know them.
• Names that match nothing leave the parent unset and surface a warning in the result summary -- the row still imports, you just see exactly which links did not land.

Two import modes, one of them destructive

• Addition (safe): upsert by name. Existing humans whose names match get their fields refreshed. Humans not in the CSV are left alone. Default mode, never deletes anything.
• NEW / Overwrite: upsert by name, then delete any human not in the CSV. Agents that escalated to a deleted human lose that link automatically; other humans that reported to a deleted human do too. Confirmation prompt before any destructive run.

Preview before you commit

• The drawer parses your CSV client-side and shows a row-by-row preview: which rows are new, which are updates, and which references will resolve.
• A live count tells you exactly how many humans NEW mode would delete -- before you run it.
• The whole import lands as a single atomic write to your draft OOS, not 50 round-trips. Up to 500 rows per file.

Find it next to "Invite member" at the top of /dashboard/team. Owners only.

Until today, getting a tile onto /dashboard/team meant either authoring an OOS file or sending an invite. That worked when you had real teammates to email, but slowed you down when you wanted to model an agent or place a known human on the chart without bringing them in yet. Two changes fix that.

Two new entry points to the create flow

• "Add to chart" button at the top of the chart, next to "Invite member." Opens the same side drawer you already use for tile editing, but in create mode -- empty fields, a Human / Agent toggle at the top, and a Create button instead of Save.
• Per-tile "+" button appears in the bottom-right corner when you hover any tile (owners only). Click it and the create drawer opens with the tile you hovered preselected as the parent -- "reports to" for humans, "escalates to" for agents. One click adds a direct report under the seat you are standing on.

Same drawer, same fields, same SOP section

• Every field from the edit drawer is available in create mode: role, mission, job description, authority level, agentic maturity, platform, status, contact email/phone, Slack ID, skills, MCPs, SOPs, KPIs.
• The Invite section and Delete button are hidden in create mode -- the rest of the panel is identical, so the visual rhythm of the chart is unchanged.
• Submit creates the tile in your draft and saves all the extra fields in one go. Reload to see it on the chart.

Agent Builder runs inside the chart now

• In agent create mode, a "Use Agent Builder" button appears at the top of the drawer. Click it and the Agent Builder slides in from the right -- same rail as the create drawer, white background, light theme.
• Just the wizard. No hero, no marketing sections, no footer. Industry, title, description, skills, tools, personality framework, review.
• On generate, the result populates the create drawer underneath: name, role, mission, skills, MCPs all filled in, with the full generated CLAUDE.md added as a SOP entry titled "Generated CLAUDE.md." The Agent Builder closes; you adjust anything you want and click Create.
• The standalone /agent-builder page is unchanged for visitors who land on it directly.

Why this matters

The seat is the unit of an org chart, not the body. Until you can put a seat down without sending an email, the chart is gated by your willingness to bother people. Now you can model the team you want -- humans you have not invited yet, agents you are still drafting -- and the chart is a working spec from the moment you put a tile on it. The Agent Builder integration closes the loop between "I need an agent for X" and "the agent is on my chart with the right SOPs inherited from its parent." Two minutes from idea to placeable seat.

Today is the pivot. OTP started as the Organization Transport Protocol for AI agents. The acronym was right; the scope was too narrow. The agent army is a slice of the organization. The whole organization is humans + agents + the SOPs that move between them. That is what OTP is for now.

SOPs as the unit of coordination

• Author once: click any agent or human on /dashboard/team and add SOPs in the side panel. Each SOP has title, trigger, steps, outputs, tools, and notes -- enough structure for AI inheritance, light enough to author in under a minute.
• Five Founder/CEO templates seeded: daily inbox triage, weekly L8, monthly stakeholder update, founder-led discovery call, quarterly Rocks-setting. Click "+ From template..." in the SOP section, pick one, edit to your voice, save. Sixty seconds to a working operating cadence.
• Purple "N SOPs" badge on every chart tile that has authored SOPs. Visual confirmation that a tile carries executable spec, not just a name.

AI agents inherit SOPs from their human

• Inheritance: when an agent escalates_to a human, the agent inherits that human's SOPs as runtime context. No copy-paste, no re-explanation when a new instance spins up.
• Copy as Agents.md / Claude.md: every agent's edit panel has a one-click button that compiles own SOPs + inherited SOPs + role/mission/authority into a markdown file, copied straight to your clipboard. Pick the format your stack expects -- AGENTS.md (cross-platform default), CLAUDE.md (Claude Code), .cursorrules (Cursor), or generic system prompt. Drop it into your runtime and the agent runs on the org's latest accountability state.
• Tooltip: hover any agent and see "Inherits N SOPs from {parent}." The SOP layer is visible at a glance.

Multi-user invitations

• Invite to claim a tile: open any human node and you will find an "Invite to claim this tile" section. Email goes out from notifications@mail.orgtp.com with a 30-day-TTL signed link.
• Invite someone new: the chart header has a "+ Invite new member" button that creates a fresh tile and fires the invite in one action -- name, email, optional role, optional reports-to.
• Accept-invite landing: the recipient lands on a page showing the org name, the tile reserved for them, and the expiry date before they sign in. Clerk handles auth; the token preserves through the redirect; the tile auto-claims on success.
• Pending invites drawer: owners get a header button (with badge count) that opens a drawer of every pending invite, with revoke buttons.
• "Claimed" pill shows on every human tile that is bound to a real member account.

Editor polish

• Contact fields on humans: email, phone, Slack ID, with small contact pills on the chart tile when populated.
• Status field with active / paused / inactive / retired / terminated. Inactive nodes render grayscale with a strike-through name -- a clean way to mark old data without losing structure.
• Explicit Delete button in the edit panel. Removing a tile also scrubs any escalates_to / reports_to / override_authority references that pointed at it, so the chart never dangles.
• Sticky filter: the All / Agents / Humans toggle persists in localStorage. Refresh the page; the view stays where you left it.

What the framing change means

OTP is no longer "the AI coordination protocol." It is the substrate for hybrid human-and-AI organizations. The chart is the surface, the SOPs are the substance, the network is the leverage. /about and the FAQ are updated.

Next up: invite-from-tile for agents (members spin up their own connected Claude instances under their tile), dotted comparison lines between same-role agents, skills taxonomy, and mobile polish.

Open /dashboard/team and your published OOS becomes a top-down org chart: agents, humans, organization, all wired by escalation and reporting lines.

• Live derivation from your OOS: the chart reads entities.agents and entities.humans from your latest draft (preferred) or published file. No new schema, no separate database. Your OOS is still the source of truth.
• Click any node to edit: a side panel opens with name, role, mission or job description, authority level, platform and status (agents), skills, and the escalates_to or reports_to dropdown. Saving creates a draft if you do not already have one.
• Drag and drop to restructure: drag any agent or human onto another box and it becomes the new child. Cycle prevention rejects drops that would create loops. The PATCH writes back to your OOS draft and the chart re-renders.
• Type filter: the All / Agents / Humans toggle re-lays out the tree to show just what you care about.
• Status banner: shows whether you are looking at a draft (with version number) or your published file. Edits never touch your published file until you republish.

If your OOS does not have entities.agents or entities.humans populated yet, the chart will look empty. Reach out and we can help you migrate. Next up: skills taxonomy, mobile polish, and add/delete nodes.

OTP's biggest update yet. We flipped the entry point: instead of asking you to publish, we're giving you something useful first. Industry coordination playbooks written from real production experience.

• 6 Industry Playbooks: Agency (34 practices), Fitness/Franchise (29), Healthcare (24), SaaS (23), Professional Services (50), and E-Commerce (43). Each practice includes what to do, why it matters, and what goes wrong without it. These are original content from teams running 10+ AI agents in production, not scraped or AI-classified consulting reports.
• Download as CLAUDE.md: One click exports any industry playbook as a CLAUDE.md file you can drop into your project. Your agents start following proven coordination patterns immediately.
• CLAUDE.md Generator: Tell us your industry, team size, and agent count. Our AI generates a complete, customized CLAUDE.md using your industry's coordination practices as context. Fallback templates ensure you always get something useful, even if the AI is having a bad day.
• Practice Voting: Upvote and downvote practices on any industry page. Community validation surfaces the practices that actually work in the real world.
• Newsletter: Weekly coordination intelligence updates delivered to your inbox. No account required, just your email. Stay informed about new practices, industry playbooks, and what's working for other AI teams.
• Homepage Refresh: Three-slide hero showcasing industry playbooks, the CLAUDE.md scanner, and newsletter signup. All 6 industries with live practice counts.

The idea is simple: come to OTP, get your industry's playbook, use it. When you're ready to share what you've learned, publish your OOS. But start with value, not a request.

Three new features that make uploading your CLAUDE.md safer, more actionable, and more fun.

• Vulnerability Scanner: Before you can publish, OTP now scans your entire system prompt for sensitive data -- API keys, passwords, database URLs, credit card numbers, SSNs, revenue figures, salary data, employee names, Slack IDs, internal file paths, billing rates, and more. 20+ detection patterns across 5 categories (credentials, financial, personal, infrastructure, business). Critical and high-severity findings block publishing until resolved. Your secrets stay secret.
• Foundation Score (0-100): Instant structural triage on upload. 15 checks surface the critical fixes that need attention right now -- not nuanced best practices, but the stuff that's obviously broken. No human override authority? No escalation paths? No error handling? Agents with no clear responsibilities? The Foundation Score catches it immediately and tells you exactly how to fix each one. Critical failures cap your score regardless of everything else.
• Share Your Score: New share button on both the scan results page and the dashboard. One click opens a modal with your score card, pre-generated social text, and share to X, LinkedIn, or clipboard. Designed for virality -- "Just scanned my AI agent system. Coordination Score: 82/100. What's yours?" Every share is an ad for OTP.

The vulnerability scanner is a trust prerequisite -- it removes the fear barrier to sharing your operating system. The Foundation Score gives instant value on first upload. And the share button turns every scan into a growth opportunity.

OTP now scores your AI coordination maturity on a 0-100 scale across 6 dimensions: Conflict Management, Escalation Structure, Workflow Clarity, Human Oversight, System Redundancy, and Authority Boundaries. The score is the product.

• Scan Results Page: Animated score ring (Lighthouse-style), 6-dimension breakdown bars with color coding, and insight cards grouped by severity. This is the "aha moment" -- upload your CLAUDE.md and see what the scanner finds.
• Fix Issues Inline: Each critical/warning insight has a "Resolve This" button. Type your resolution, it generates a claim, your score ticks up in real time. The scan page IS the diagnostic session.
• One-Click Publish: After fixing issues, "Publish to OTP Network" does everything in one click -- auto-fix, create OOS, publish, redirect to your live page. No confusing intermediate steps.
• Dashboard Overhaul: Your dashboard now shows the same score ring and dimension bars. Quick stats (claims, best practices matched, learnings, connected orgs), quick actions (Capture Learning, System Prompt, Re-scan), network activity from other orgs, and OOS file management.
• Import-First Publish: The publish page now leads with "Upload File" (drag-drop zone for CLAUDE.md) instead of hiding it as a "power user" option. The wizard is secondary for people starting from scratch.
• CLAUDE.md Parser: New /scanner/from-text endpoint extracts agents, systems, workflows, and oversight patterns from raw CLAUDE.md files. No more "Scanner could not analyze this content" errors.
• Copy as System Prompt: One button on any OOS detail page formats your claims into a compact, token-efficient block for pasting into CLAUDE.md. Shows Token Efficiency Index.

The creation experience is now the product. You don't need the network to get value from OTP -- the score alone tells you where your agent coordination is strong and where it's exposed.

OTP is now a living system. When an agent in your team makes a mistake and you correct it, that correction becomes coordination intelligence on the network -- immediately, automatically, for every organization to learn from.

• Auto-capture: When you correct an agent's output, the agent automatically calls capture_learning with what failed, what to do instead, and why. Every correction is a learning. No manual step.
• Auto-publish: Learnings go directly to your published OOS and the OTP network. No draft step, no delay. Your correction is available to the entire network within seconds.
• Auto-pull: Before executing their main task, agents check OTP for relevant learnings: "Has anyone (including other orgs) learned something about what I'm about to do?" If yes, they follow the learning instead of repeating the mistake.
• Cross-org learning: When another organization discovers a coordination failure that matches your agent setup, OTP surfaces it. Their failure becomes your prevention.

This is the OTP flywheel: agents operate → humans correct → corrections become intelligence → all agents improve → fewer corrections needed. Sneeze It is the first organization running this loop live.

OTP is now a multi-publisher best practices platform. We scraped, structured, and indexed AI knowledge from 8 authoritative sources: Google (686 ML terms), Amazon Web Services (254 cloud AI terms), DAIR.AI (236 prompt engineering techniques), McFadyen Digital (209 commerce AI practices), Hopsworks (152 MLOps terms), Accenture (8 enterprise case studies), Deloitte (7 AI use cases), and Bain & Company (2 strategy frameworks). Each publisher gets a profile with attribution, and every practice links back to its source.

• Publisher profiles: A new expert type. Each publisher has a full profile, linked best practices, and attribution on every card.
• OOS-connected matching: Best practices are matched to your OOS using Jaccard similarity with concept synonyms. The "Matched to My OOS" view shows only practices relevant to your coordination patterns, sorted by relevance score.
• Implement and Ingest: Click "Implement" on any best practice to see the full definition, publisher credit, and which organizations align with that pattern. Click "Ingest into my OOS" to add it as a claim to your draft OOS.
• Best practices on OOS detail: Each published OOS now shows a "Relevant Best Practices" section with matched practices, scores, and source links.
• Bidirectional matching: When viewing a best practice, see which organizations implement that pattern -- creating a two-way discovery network between publishers and practitioners.

This introduces a new expert type: Publisher. While Consultants help you implement, Publishers contribute knowledge databases that enrich the platform for everyone.

• OOS limits raised 3x: Maximum word count increased from 5,000 to 15,000 words. Section claim caps tripled (e.g. 10 to 30). Upload limit raised to 2MB. Minimum lowered to 500 words for starter OOS files.
• MCP server auto-detection: The auto-fixer now scans OOS content against 30+ known tools (Slack, Gmail, Google Ads, Meta Ads, Todoist, etc.) and populates the Infrastructure Graph automatically. All published OOS files have been enriched.
• Publish wizard: tool collection: Step 2 now includes checkboxes for 20 common MCP servers/integrations alongside AI platforms. Select what your agents connect to -- it goes straight into the Infrastructure Graph.
• Agentic Level Calculator v2: Expanded from rigid exact-match keywords to 100+ semantic patterns. Checks frontmatter metadata (platforms, MCP servers). All orgs rescored -- most jumped from L2 to L5-L8.
• Sign In page: Dedicated /sign-in page with Clerk integration. Sign In button now visible in the navigation for all visitors.