{ "engine": "TeamStation Research Publishing Operating System", "engine_version": "0.5.0", "topic": "Engineering Capacity as an Operating System", "slug": "engineering-capacity-operating-system-blueprint", "template": "arxiv", "publication_standard": { "label": "arXiv", "page_size": "letter", "margins": { "top": "1in", "right": "1in", "bottom": "1in", "left": "1in" }, "citation_style": "numeric", "bibliography": "BibTeX plain", "author_block": "centered title page", "acknowledgements": "before references", "figure_placement": "htbp", "appendix_format": "appendix sections after references", "latex_documentclass": "article" }, "typography": { "title": { "font_size_pt": 18, "weight": "bold", "alignment": "center" }, "running_title": { "font_size_pt": 10, "weight": "regular", "alignment": "left" }, "authors": { "font_size_pt": 12, "weight": "regular", "alignment": "center" }, "affiliations": { "font_size_pt": 10, "weight": "regular", "alignment": "center" }, "abstract_heading": { "font_size_pt": 14, "weight": "bold", "alignment": "left" }, "heading_1": { "font_size_pt": 14, "weight": "bold", "alignment": "left" }, "heading_2": { "font_size_pt": 12, "weight": "bold", "alignment": "left" }, "body": { "font_size_pt": 11, "weight": "regular", "alignment": "left", "line_spacing": 1.15 }, "paragraph": { "space_after_pt": 6, "indent_first_line": false }, "figure_caption": { "font_size_pt": 9, "weight": "regular", "alignment": "center" }, "table_caption": { "font_size_pt": 9, "weight": "regular", "alignment": "center" }, "code": { "font_family": "JetBrains Mono", "font_size_pt": 9, "weight": "regular" }, "references": { "font_size_pt": 10, "weight": "regular", "hanging_indent_in": 0.25 }, "footnotes": { "font_size_pt": 9, "weight": "regular" } }, "generated_at": "2026-07-09T16:25:28Z", "authors": [ { "name": "Lonnie McRorey", "role": "Founder and CEO", "affiliation": "TeamStation AI", "location": "Boston, Massachusetts", "orcid": "https://orcid.org/0009-0001-5351-190X" } ], "publisher": "TeamStation AI", "keywords": [ "engineering capacity", "engineering operating system", "DORA", "SPACE", "Team Topologies", "AI governance", "agentic SDLC", "engineering telemetry" ], "subject_classification": "Computer Science - Software Engineering", "classification": "ACM CCS: Software and its engineering", "license": "CC BY 4.0", "evidence_tags": [ "Supported", "Needs Citation", "Internal Research", "External Validation", "Observation", "Hypothesis", "Opinion", "Future Work" ], "source_count": 18, "learning_source_count": 14, "claims_checked": [ "Engineering capacity should be modeled as an operating system rather than a staffing problem." ], "claim_support_result": { "checked_at": "2026-07-07T19:13:05.171418+00:00", "sensitivity_max": "internal", "claim_count": 1, "status_counts": { "supported": 1 }, "review_required_count": 0, "policy": "Lexical source-support check. Human review required for legal, science, security, pricing, compliance, superiority, or guarantee claims.", "results": [ { "claim": "Engineering capacity should be modeled as an operating system rather than a staffing problem.", "support_status": "supported", "best_coverage": 1, "evidence_count": 8, "required_sources": 2, "claim_tokens": [ "capacity", "engineering", "modeled", "operating", "problem", "rather", "should", "staffing", "system", "than" ], "high_risk_terms": [], "review_required": false, "evidence": [ { "uri": "company://company.methods/engineering/public/api/research/engineering-operating-system.json", "title": "engineering-operating-system.json", "snippet": "{ \"id\": \"engineering-capacity-os-v3\", \"title\": \"Engineering Capacity Operating System Research\", \"display_title\": \"Engineering Capacity Operating System\", \"version\": \"3.0\", \"schema_version\": \"3.0.0\", \"status\": \"canonical_research_node\", \"human_route\": \"https://engineering.teamstation.dev/research/engineering-operating-system\", \"json_route\": \"https://engineering.teamstation.dev/api/research/engineering", "coverage": 1, "matched_tokens": [ "capacity", "engineering", "modeled", "operating", "problem", "rather", "should", "staffing", "system", "than" ], "score": 104, "metadata": { "bytes": 576354, "content_role": "structured_data", "extension": ".json", "last_indexed_at": "2026-07-07T19:11:42.591423+00:00", "mtime_ns": 1783434865586965800, "namespace": "company.methods", "project": "engineering", "sensitivity": "internal", "sha256": "bc98b3efd83eeae72dcee5af84849df75b03d42d2dd3613a8dacb575de18cc11", "source_path": "Engineering/public/api/research/engineering-operating-system.json", "source_type": "doc", "title": "engineering-operating-system.json", "topics": [ "agent_core", "agent_skills", "axiom_cortex", "brand", "capabilities", "marketing", "pricing", "science_methods", "security", "talent_operations", "teamlemetry", "validation", "workflow" ], "uri": "company://company.methods/engineering/public/api/research/engineering-operating-system.json" } }, { "uri": "company://company.methods/engineering/public/api/research/engineering-operating-system.v3.json", "title": "engineering-operating-system.v3.json", "snippet": "{ \"id\": \"engineering-capacity-os-v3\", \"title\": \"Engineering Capacity Operating System Research\", \"display_title\": \"Engineering Capacity Operating System\", \"version\": \"3.0\", \"schema_version\": \"3.0.0\", \"status\": \"canonical_research_node\", \"human_route\": \"https://engineering.teamstation.dev/research/engineering-operating-system\", \"json_route\": \"https://engineering.teamstation.dev/api/research/engineering", "coverage": 1, "matched_tokens": [ "capacity", "engineering", "modeled", "operating", "problem", "rather", "should", "staffing", "system", "than" ], "score": 104, "metadata": { "bytes": 576354, "content_role": "structured_data", "extension": ".json", "last_indexed_at": "2026-07-07T19:11:42.591423+00:00", "mtime_ns": 1783434865587077400, "namespace": "company.methods", "project": "engineering", "sensitivity": "internal", "sha256": "bc98b3efd83eeae72dcee5af84849df75b03d42d2dd3613a8dacb575de18cc11", "source_path": "Engineering/public/api/research/engineering-operating-system.v3.json", "source_type": "doc", "title": "engineering-operating-system.v3.json", "topics": [ "agent_core", "agent_skills", "axiom_cortex", "brand", "capabilities", "marketing", "pricing", "science_methods", "security", "talent_operations", "teamlemetry", "validation", "workflow" ], "uri": "company://company.methods/engineering/public/api/research/engineering-operating-system.v3.json" } }, { "uri": "company://company.methods/engineering/public/api/research/engineering-operating-system.md", "title": "Engineering Capacity Operating System", "snippet": "# Engineering Capacity Operating System Canonical title: Engineering Capacity Operating System Research Version: 3.0 Schema version: 3.0.0 Status: canonical_research_node Human route: https://engineering.teamstation.dev/research/engineering-operating-system JSON route: https://engineering.teamstation.dev/api/research/engineering-operating-system Static JSON route: https://engineering.teamstation.dev/api/research/eng", "coverage": 1, "matched_tokens": [ "capacity", "engineering", "modeled", "operating", "problem", "rather", "should", "staffing", "system", "than" ], "score": 100, "metadata": { "bytes": 42947, "content_role": "documentation", "extension": ".md", "last_indexed_at": "2026-07-07T19:11:42.591423+00:00", "mtime_ns": 1783434865586827800, "namespace": "company.methods", "project": "engineering", "sensitivity": "internal", "sha256": "51424481617e65b8e55b510ace57afca397506a22ef1897d7ea673917e02ff73", "source_path": "Engineering/public/api/research/engineering-operating-system.md", "source_type": "doc", "title": "Engineering Capacity Operating System", "topics": [ "agent_core", "agent_skills", "axiom_cortex", "brand", "capabilities", "marketing", "pricing", "science_methods", "security", "talent_operations", "teamlemetry", "validation", "workflow" ], "uri": "company://company.methods/engineering/public/api/research/engineering-operating-system.md" } }, { "uri": "company://company.agent_core/agent_core/research-os/engineering-capacity-operating-system-blueprint/metadata.json", "title": "metadata.json", "snippet": "{ \"engine\": \"TeamStation Research Publishing Operating System\", \"engine_version\": \"0.4.0\", \"topic\": \"Engineering Capacity as an Operating System\", \"slug\": \"engineering-capacity-operating-system-blueprint\", \"template\": \"arxiv\", \"publication_standard\": { \"label\": \"arXiv\", \"page_size\": \"letter\", \"margins\": { \"top\": \"1in\", \"right\": \"1in\", \"bottom\": \"1in\", \"left\": \"1in\"", "coverage": 1, "matched_tokens": [ "capacity", "engineering", "modeled", "operating", "problem", "rather", "should", "staffing", "system", "than" ], "score": 100, "metadata": { "bytes": 24192, "content_role": "documentation", "extension": ".json", "last_indexed_at": "2026-07-07T19:11:42.591423+00:00", "mtime_ns": 1783451472620325600, "namespace": "company.agent_core", "project": "agent_core", "sensitivity": "internal", "sha256": "251858b5d1ec7ce89a6066cfe5d337d2d73791b0b042637acea899e98e752237", "source_path": "docs/teamstation-agent-core/research-os/engineering-capacity-operating-system-blueprint/metadata.json", "source_type": "doc", "title": "metadata.json", "topics": [ "agent_core", "agent_skills", "brand", "capabilities", "deos", "finance", "marketing", "nebula", "pricing", "science_methods", "security", "talent_operations", "teamlemetry", "validation", "workflow" ], "uri": "company://company.agent_core/agent_core/research-os/engineering-capacity-operating-system-blueprint/metadata.json" } }, { "uri": "company://company.methods/engineering/data/research/engineering-os.md", "title": "Engineering Capacity Operating System", "snippet": "# Engineering Capacity Operating System Canonical title: Engineering Capacity Operating System Research Version: 3.0 Schema version: 3.0.0 Status: canonical_research_node Human route: https://engineering.teamstation.dev/research/engineering-operating-system JSON route: https://engineering.teamstation.dev/api/research/engineering-operating-system Static JSON route: https://engineering.teamstation.dev/api/research/eng", "coverage": 1, "matched_tokens": [ "capacity", "engineering", "modeled", "operating", "problem", "rather", "should", "staffing", "system", "than" ], "score": 90, "metadata": { "bytes": 42947, "content_role": "documentation", "extension": ".md", "last_indexed_at": "2026-07-07T19:11:42.591423+00:00", "mtime_ns": 1783428052151438600, "namespace": "company.methods", "project": "engineering", "sensitivity": "internal", "sha256": "51424481617e65b8e55b510ace57afca397506a22ef1897d7ea673917e02ff73", "source_path": "Engineering/data/research/engineering-os.md", "source_type": "doc", "title": "Engineering Capacity Operating System", "topics": [ "agent_core", "agent_skills", "axiom_cortex", "brand", "capabilities", "marketing", "pricing", "science_methods", "security", "talent_operations", "teamlemetry", "validation", "workflow" ], "uri": "company://company.methods/engineering/data/research/engineering-os.md" } }, { "uri": "company://company.teamstation/teamstation_ai/functions/lib/capacity-intelligence.js", "title": "capacity-intelligence.js", "snippet": "import { STANDARD_MONTHLY_HOURS, countryPlanningProfiles, estimateCapacityPlan, includedCostCategories, includedPricingControls, includedSeatStack, rolePricingProfiles, seniorityLevels } from '../../data/pricingModel.js'; import { aiEngineeringEntities } from '../../data/aiEngineeringOntology.js'; import { aiTechnologyCatalog } from '../../data/aiTechnologyCatalog.js'; import { aiTransformationOntol", "coverage": 1, "matched_tokens": [ "capacity", "engineering", "modeled", "operating", "problem", "rather", "should", "staffing", "system", "than" ], "score": 79, "metadata": { "bytes": 361455, "content_role": "source_code", "extension": ".js", "last_indexed_at": "2026-07-07T19:11:42.591423+00:00", "mtime_ns": 1783182688577404700, "namespace": "company.teamstation", "project": "teamstation_ai", "sensitivity": "internal", "sha256": "33696606e6a946eb6dbaf6770a89779d6e99a7ee2adbd1b4a00a86853fe62d57", "source_path": "TeamStation-AI/functions/lib/capacity-intelligence.js", "source_type": "code", "title": "capacity-intelligence.js", "topics": [ "agent_core", "agent_skills", "axiom_cortex", "brand", "capabilities", "deos", "finance", "nebula", "pricing", "science_methods", "security", "talent_operations", "teamlemetry", "validation", "workflow" ], "uri": "company://company.teamstation/teamstation_ai/functions/lib/capacity-intelligence.js" } }, { "uri": "company://company.methods/engineering/data/research/engineering-os.json", "title": "engineering-os.json", "snippet": "{ \"id\": \"engineering-capacity-os-v3\", \"title\": \"Engineering Capacity Operating System Research\", \"display_title\": \"Engineering Capacity Operating System\", \"version\": \"3.0\", \"schema_version\": \"3.0.0\", \"status\": \"canonical_research_node\", \"human_route\": \"https://engineering.teamstation.dev/research/engineering-operating-system\", \"json_route\": \"https://engineering.teamstation.dev/api/research/engineering", "coverage": 1, "matched_tokens": [ "capacity", "engineering", "modeled", "operating", "problem", "rather", "should", "staffing", "system", "than" ], "score": 76, "metadata": { "bytes": 284892, "content_role": "structured_data", "extension": ".json", "last_indexed_at": "2026-07-07T19:11:42.591423+00:00", "mtime_ns": 1783428052151459800, "namespace": "company.methods", "project": "engineering", "sensitivity": "internal", "sha256": "1d67dbce856be4a21568936cb182766a69bc0d4f18009c22ace8279de0791a67", "source_path": "Engineering/data/research/engineering-os.json", "source_type": "doc", "title": "engineering-os.json", "topics": [ "agent_core", "agent_skills", "axiom_cortex", "brand", "capabilities", "marketing", "pricing", "science_methods", "security", "talent_operations", "teamlemetry", "validation", "workflow" ], "uri": "company://company.methods/engineering/data/research/engineering-os.json" } }, { "uri": "company://company.teamstation/teamstation_ai/public/llms-full.txt", "title": "llms-full.txt", "snippet": "# TeamStation AI Full Agentic Operating Doctrine Canonical: https://teamstation.dev/llms-full.txt Short directive: https://teamstation.dev/llms.txt AI guidance: https://teamstation.dev/.well-known/ai.txt OpenAPI JSON: https://teamstation.dev/openapi.json OpenAPI YAML: https://teamstation.dev/openapi.yaml MCP server card: https://teamstation.dev/.well-known/mcp/server-card.json Cloudflare AI Search MCP endpoint: http", "coverage": 1, "matched_tokens": [ "capacity", "engineering", "modeled", "operating", "problem", "rather", "should", "staffing", "system", "than" ], "score": 72, "metadata": { "bytes": 225261, "content_role": "documentation", "extension": ".txt", "last_indexed_at": "2026-07-07T19:11:42.591423+00:00", "mtime_ns": 1783450282059851800, "namespace": "company.teamstation", "project": "teamstation_ai", "sensitivity": "public", "sha256": "e13ab11c481d3871a78a6c5ddfe01ce498e58e00043156251e829589cc47e684", "source_path": "TeamStation-AI/public/llms-full.txt", "source_type": "code", "title": "llms-full.txt", "topics": [ "agent_core", "agent_skills", "axiom_cortex", "brand", "capabilities", "deos", "marketing", "nebula", "pricing", "science_methods", "security", "talent_operations", "teamlemetry", "validation", "workflow" ], "uri": "company://company.teamstation/teamstation_ai/public/llms-full.txt" } } ] } ], "index": { "source": "cache", "document_count": 10634, "inventory_hash": "ef8f7af244982db5425bc0e2533e34226f55a3ae37359744a67f10b8d9096b57", "manifest_hash": "06de28129f727af88333e63dff8a7982e90e449c9bf86ef63d9737bea5dfab79" } }, "quality_gates": [ { "name": "minimum_source_count", "status": "pass", "detail": "9 source(s) retrieved; minimum is 4." }, { "name": "engineering_doctrine_presence", "status": "pass", "detail": "Engineering Research sources: 3." }, { "name": "main_website_or_research_presence", "status": "pass", "detail": "Requires at least one main website or TeamStation research source." }, { "name": "semantic_cluster_coverage", "status": "pass", "detail": "Clusters found: delivery_operations, engineering_doctrine, evidence, methodology, ontology, system_architecture." }, { "name": "public_source_boundary", "status": "pass", "detail": "Internal sources included." }, { "name": "claim_support", "status": "pass", "detail": "All provided claims have support." }, { "name": "citation_integrity", "status": "pass", "detail": "Every source has URI, source path, and checksum." } ], "paper_blueprint": { "recommended_title": "Engineering Capacity as an Operating System", "target_length_pages": "25-40", "novelty": "AI should never recommend organizational change before classifying the quality of its evidence. Hiring, outsourcing, insourcing, vendor replacement, and automation are topology choices, not default answers.", "academic_neutrality_rule": "Present the model as a general systems contribution that any organization can evaluate, implement, critique, or extend. Do not frame the paper as the TeamStation way." }, "status": "operationally_validated_working_paper_human_review_required", "integrity": { "status": "pass", "blocker_count": 0, "author_action_count": 7, "failed_count": 7 }, "authorship_quality": { "status": "fail", "human_reviewed": false, "failed_count": 1, "citation_density": 3.54, "generic_marker_count": 0 }, "self_learning": { "enabled": true, "voice_gate_status": "pass", "research_opportunity_count": 4, "mcp_write_status": "not_written_requires_approval" }, "title": "Engineering Capacity as an Operating System", "subtitle": "A systems model for AI governed software delivery, evidence classified topology decisions, and decision grade engineering capacity", "publication_type": "workingpaper", "word_count": 8570, "version": "0.5 operational validation boundary draft", "publisher_location": "Boston, Massachusetts", "publisher_logo": "https://engineering.teamstation.dev/teamstation-logo-lockup-dark.svg", "company_context": { "name": "TeamStation AI", "description": "Distributed Engineering Operating System research, product, and publishing context.", "founder_and_ceo": "Lonnie McRorey", "location": "Boston, Massachusetts", "public_site": "https://teamstation.dev/", "engineering_doctrine_site": "https://engineering.teamstation.dev/" }, "teamstation_science_corpus": [ { "id": "TSDEOS2026", "title": "Distributed Engineering Operating Systems", "author": "TeamStation AI Research", "year": "2026", "url": "https://teamstation.dev/research/articles/distributed-engineering-operating-systems-control-plane-model", "role": "Public TeamStation research article defining the control plane model for distributed engineering operating systems.", "source_path": "TeamStation-AI/public/markdown/research/articles/distributed-engineering-operating-systems-control-plane-model.md", "evidence_class": "MCP supported public corpus source" }, { "id": "TSAXIOM2026", "title": "Axiom Cortex for LATAM Agentic Engineering", "author": "Lonnie McRorey", "year": "2026", "url": "https://teamstation.dev/research/articles/axiom-cortex-latin-america-agentic-engineering-alignment", "role": "Public research source for mental shape, cognitive evaluation, LATAM engineering alignment, and agentic workflow fit.", "source_path": "TeamStation-AI/public/markdown/research/articles/axiom-cortex-latin-america-agentic-engineering-alignment.md", "evidence_class": "MCP supported public corpus source" }, { "id": "TSNEWSDEOS2026", "title": "TeamStation Distributed Engineering OS", "author": "Lonnie McRorey", "year": "2026", "url": "https://teamstation.dev/research/articles/teamstation-ai-publishes-distributed-engineering-os-model-for-agentic-ai-teams", "role": "Public company research note connecting TeamStation to the Distributed Engineering OS model for agentic AI teams.", "source_path": "TeamStation-AI/public/markdown/research/articles/teamstation-ai-publishes-distributed-engineering-os-model-for-agentic-ai-teams.md", "evidence_class": "MCP supported public corpus source" }, { "id": "TSCF2026", "title": "Cognitive Fidelity and the Turing Trap", "author": "TeamStation AI R&D Lab Staff", "year": "2026", "url": "https://teamstation.dev/research/articles/cognitive-fidelity-and-the-turing-trap", "role": "Public TeamStation science source for cognitive fidelity, validation quality, and the risk of confusing imitation with real engineering judgment.", "source_path": "TeamStation-AI/public/markdown/research/articles/cognitive-fidelity-and-the-turing-trap.md", "evidence_class": "Local public corpus source" }, { "id": "TSTOPOS2026", "title": "Agentic Team Topologies for CTOs and CIOs", "author": "TeamStation AI R&D Lab Staff", "year": "2026", "url": "https://teamstation.dev/research/articles/team-topologies-in-the-agentic-workflow-era-beyond-2026", "role": "Public TeamStation research source for team topology changes in agentic SDLC workflows.", "source_path": "TeamStation-AI/public/markdown/research/articles/team-topologies-in-the-agentic-workflow-era-beyond-2026.md", "evidence_class": "Local public corpus source" }, { "id": "TSTEAMTOPO2026", "title": "Software Engineering Team Topologies for 2026", "author": "TeamStation AI R&D Lab Staff", "year": "2026", "url": "https://teamstation.dev/research/articles/software-engineering-team-topologies-for-2026", "role": "Public TeamStation research source for engineering team topology patterns before and during agentic workflow adoption.", "source_path": "TeamStation-AI/public/markdown/research/articles/software-engineering-team-topologies-for-2026.md", "evidence_class": "Local public corpus source" }, { "id": "TSHIDDENMATH2026", "title": "Hidden Math of Distributed Engineering Failure", "author": "TeamStation AI R&D Lab Staff", "year": "2026", "url": "https://teamstation.dev/research/articles/the-hidden-math-behind-distributed-engineering-failure", "role": "Public TeamStation research source for coordination cost, distributed execution failure, and hidden capacity loss.", "source_path": "TeamStation-AI/public/markdown/research/articles/the-hidden-math-behind-distributed-engineering-failure.md", "evidence_class": "Local public corpus source" }, { "id": "TSAGENTICLATAM2026", "title": "2027 Agentic Team Topologies in LATAM", "author": "TeamStation AI R&D Lab Staff", "year": "2026", "url": "https://teamstation.dev/research/articles/the-2027-blueprint-for-agentic-engineering-team-topologies-in-latin-america", "role": "Public TeamStation research source for agentic engineering squad design, LATAM topology, and future capacity planning.", "source_path": "TeamStation-AI/public/markdown/research/articles/the-2027-blueprint-for-agentic-engineering-team-topologies-in-latin-america.md", "evidence_class": "Local public corpus source" }, { "id": "TSDOCTRINE2026", "title": "Engineering Capacity Operating System Research", "author": "TeamStation Engineering", "year": "2026", "url": "https://engineering.teamstation.dev/research/engineering-operating-system", "role": "Canonical Engineering Doctrine research node for the Engineering Capacity Operating System.", "source_path": "Engineering/dist/api/research/engineering-operating-system.json", "evidence_class": "MCP supported canonical doctrine node" }, { "id": "TSDOCTRINEMD2026", "title": "Engineering Capacity Operating System Markdown Source", "author": "TeamStation Engineering", "year": "2026", "url": "https://engineering.teamstation.dev/api/research/engineering-operating-system.md", "role": "Machine readable Markdown route for the canonical Engineering Capacity OS source.", "source_path": "Engineering/dist/api/research/engineering-operating-system.md", "evidence_class": "MCP supported canonical doctrine node" }, { "id": "TSCOGFIDELITYDOCTRINE2026", "title": "Cognitive Fidelity Doctrine", "author": "TeamStation Engineering", "year": "2026", "url": "https://engineering.teamstation.dev/quality/cognitive-fidelity/", "role": "Engineering Doctrine proof layer for cognitive fidelity, quality economics, and validation posture.", "source_path": "Engineering/dist/markdown/quality/cognitive-fidelity.md", "evidence_class": "Local doctrine source" }, { "id": "TSAGENTICWORKFLOWDOCTRINE2026", "title": "Agentic Engineering Workflows in Distributed Team Topologies", "author": "TeamStation Engineering", "year": "2026", "url": "https://engineering.teamstation.dev/teams/agentic-development-workflows/", "role": "Engineering Doctrine source for agentic workflow, sequential probability, incentives, replacement kinetics, and team topology math.", "source_path": "Engineering/dist/markdown/teams/agentic-development-workflows.md", "evidence_class": "Local doctrine source" } ], "glossary": [ { "term": "Agentic loop", "definition": "A governed cycle where a human, AI agent, tool, source system, and validation gate turn intent into checked output." }, { "term": "Axiom Cortex", "definition": "TeamStation's cognitive evaluation layer for mental shape, engineering judgment, role fit, and agentic workflow alignment." }, { "term": "Capacity Intelligence", "definition": "The subsystem that estimates usable capacity after cognitive load, review limits, interruptions, topology, and decision latency are accounted for." }, { "term": "Decision grade telemetry", "definition": "Operational signal with known source, definition, freshness, bias, and direct connection to a capacity or governance decision." }, { "term": "Distributed Engineering Operating System", "definition": "The TeamStation operating model connecting talent signal, team topology, governance, telemetry, compliance, payroll, devices, MDM, and delivery controls into one source of truth." }, { "term": "Engineering Capacity OS", "definition": "The research model proposed in the paper for treating capacity as knowledge, execution, governance, topology, telemetry, and automation, not as headcount alone." }, { "term": "Evidence classification", "definition": "The rule that every claim is tagged as observed, modeled, directional, unknown, opinion, hypothesis, future work, internal research, or external validation before recommendation." }, { "term": "Governed Agentic SDLC", "definition": "A software delivery system where AI assistants and agents operate inside explicit permissions, evidence capture, approval gates, rollback paths, and human ownership." }, { "term": "Knowledge Architecture", "definition": "The memory layer of the engineering system: architecture decisions, ownership, runbooks, domain rules, glossary, onboarding path, and incident learning." }, { "term": "MCP", "definition": "Model Context Protocol, used here as the governed retrieval and tool layer connecting agents to TeamStation research, engineering doctrine, APIs, diagrams, and knowledge sources." }, { "term": "Nebula Talent Graph", "definition": "TeamStation's talent intelligence layer for representing engineering capability, signal, role alignment, and topology fit." }, { "term": "Topology choice", "definition": "A decision about where work should live: internal team, platform team, enabling team, nearshore pod, vendor, agent, automation lane, or no expansion." } ], "package_status": "Operationally validated working paper draft. Not peer reviewed. Not independently replicated. Do not publish without human review, citation review, and final package validation.", "evidence_policy": { "teamstation_sources": "Internal research context and traceability, not independent external validation.", "external_sources": "Public references only where listed in BibTeX, RIS, CSL JSON, schema metadata, and the manuscript reference list.", "fictional_walkthrough": "Demonstration scenario only. Not client data.", "excluded_data": "No client telemetry, private customer records, payroll records, health records, legal records, raw credentials, or confidential candidate data.", "mcp_claim_support_checked_at": "2026-07-08", "mcp_claim_support_status": "central thesis, TeamStation operating model, science corpus coverage, package contents, and MCP retrieval role returned supported in TeamStation Brain lexical source-support checks" }, "validation_boundary": { "operational_validation": "Completed inside TeamStation production engineering operating system using operational observations, delivery telemetry, topology decisions, governance workflows, and capacity assessments.", "internal_empirical_validation": "Supported by TeamStation controlled evidence and production operating model records.", "external_validation": "Not claimed. Independent external validation remains future work.", "academic_replication": "Not claimed. Independent academic replication remains future work.", "peer_review": "Not claimed." }, "date_published": "2026-07-09", "date_modified": "2026-07-10", "canonical_url": "https://engineering.teamstation.dev/research/engineering-operating-system/paper/", "pdf_url": "https://engineering.teamstation.dev/api/research/engineering-capacity-paper/paper.pdf" }