Nine Complete Enterprise Sites, One AI Prototyping Lab Tony Malott · Source dated 2026-07-14 https://shareplane.malott.ai/artifacts/nine-complete-enterprise-sites-one-ai-prototyping-lab/ Skip to content SharePlane Prototype Lab Open gallery Why Gallery Architecture Repository Roles Manageability SharePoint Interactive SharePlane artifact Nine complete enterprise sites. One AI prototyping lab. This artifact demonstrates what skilled human judgment, current-generation AI models, reusable design authority, deterministic tooling, and disciplined validation can produce without first constructing a traditional application platform. Each child is a complete self-contained website, preserved byte-for-byte inside this parent review environment. Review the prototypes Understand the system 9 complete site prototypes 3 creative rounds 90 customer route views 54 working calculators 126 lifecycle stage instances 934,474 source HTML bytes Why make it Show the product before funding the platform Stakeholders can inspect complete customer experiences, interactions, calculators, information architecture, agent surfaces, and responsive behavior before anyone commits to a production stack. What it proves AI speed becomes useful only when governed The demonstration is not merely that models can emit HTML. The useful capability is preserving meaning, applying visual authority, testing behavior, separating human and agent surfaces, and retaining exact evidence. What it avoids Premature platform gravity The prototypes do not require a framework, database, package manager, analytics layer, runtime AI service, remote assets, or enterprise integration to be useful for product and architecture decisions. What remains human Authority, judgment, and acceptance Humans define the service, select the direction, approve public boundaries, and decide whether the prototype earns implementation. Automation accelerates execution; it does not inherit accountability. Byte-preserved nested sites Review every prototype inside one artifact. Select a site, inspect it in the embedded frame, verify its source identity, download the original HTML, or compare two candidates side by side. 1.01 Lifecycle Command Center Lifecycle stages are the primary navigation grammar; services and calculators attach to the journey. 423252e62c670524… 1.02 Service Atlas Customer intent and service classification drive discovery, comparison, and fit. b1e3eb351f48958d… 1.03 Engineering Confidence System Planning, readiness, resilience, assumptions, and technical confidence lead the experience. f26d6fee4cc8f347… 2.04 Operational Broadsheet An editorial enterprise publication system with linear indexes and serious planning worksheets. e7882274c4bc5906… 2.05 Engineering Blueprint A rectilinear engineering specification built from linework, gates, matrices, and configuration sheets. 71369c6efcd6a3e7… 2.06 Service Field Manual A premium operating handbook organized around chapters, handoffs, checklists, and responsibility ledgers. e68005269aeaf6de… 3.07 Context Ledger A persistent dual surface pairing route authority, human guidance, and synchronized agent context. 84ea9f829668df26… 3.08 Authority Weave A provenance-first experience connecting semantic source, human projection, agent projection, and human gates. 2979aac500c3167e… 3.09 Briefing Compiler A task-led compiler generating equivalent human briefs and bounded agent packets from one semantic registry. e096934ad38ac25c… Round 1 Lifecycle Command Center Reload Verify SHA-256 Download original Full screen Source identity Not verified Compare: Lifecycle Command Center Service Atlas Engineering Confidence System Operational Broadsheet Engineering Blueprint Service Field Manual Context Ledger Authority Weave Briefing Compiler Lifecycle Command Center Service Atlas Engineering Confidence System Operational Broadsheet Engineering Blueprint Service Field Manual Context Ledger Authority Weave Briefing Compiler Load comparison Static nested-artifact architecture How one HTML contains nine complete HTMLs. The parent remains a normal SharePlane artifact. The child sites are exact byte streams encoded inside inert script payloads. Local JavaScript decodes only the selected candidate into an iframe. Nothing is fetched from a server. 01 Canonical artifact artifact.json records identity, claims, provenance, relationships, runtime exception, and human gates. 02 Locked parent page page.html contains the teaching narrative, gallery controls, inventory, and all child payloads. 03 Embedded prototypes Nine original HTML files are Base64-encoded without rewriting their bytes. 04 Local review runtime The selected payload is decoded into sandboxed iframe.srcdoc ; compare mode loads two independently. A nonpersistent storage shim is injected only into the review rendering so local interactions work without same-origin authority. Original payloads and downloads remain exact. 05 Generated projections SharePlane builds catalog, graph, context, agent package, receipt, sitemap, and discovery outputs. Runtime boundary: the parent uses dependency-free progressive JavaScript because interactive inspection is the artifact’s purpose. The explanatory content and inventory remain readable without it. There is no runtime AI, network call, analytics, tracker, remote font, external script, or database. Context as code How the repository works. One authoritative record content/artifacts//artifact.json governs structured identity, status, sources, claims, relationships, presentation, runtime, and validation. One human source content/artifacts//page.html is the locked parent review experience. The embedded children retain their own byte identities. Build-time compiler Python tooling converts canonical records into the public site, catalog, graph, JSON-LD, contexts, agent packages, manifests, and receipts. Validation before publication Schemas, source hashes, runtime posture, copy identity, links, graph edges, agent boundaries, deterministic builds, and rendered UAT are checked before merge. Static public runtime The deployed artifact is ordinary static HTML and generated JSON. There is no service to patch, database to migrate, or application server to keep emotionally supported. Receipts preserve evidence Exact source, build, generated-tree, package, and review identities let later readers distinguish current authority from historical evidence. Authority does not emerge from tool access How the roles are divided. Tony Malott Owns product intent, semantic approval, public-safe boundaries, candidate selection, Creative Lock, acceptance, merge authority, and publication judgment. ChatGPT Co-develops thesis, architecture, information design, candidate systems, public framing, source packaging, and the bounded implementation contract. Codex Performs mechanical repository execution after authority is locked: exact placement, schema translation, hashing, build, validation, browser UAT, draft PR, and receipts. It does not rewrite or select. SharePlane compiler and validators Generate deterministic public and machine projections, enforce invariants, reject drift, and provide reproducible evidence. Passing validation is not human approval. Why this is easier to manage Manage the source once. Regenerate everything else. Exact changes are visible Git shows what changed, who changed it, and which source identity produced the output. A complete artifact can be reviewed as code, rendered experience, and machine record. Rollback is ordinary The source, metadata, schemas, and receipts are versioned together. Reverting a commit restores the complete known state without reconstructing a page from UI history. Automation is deterministic Catalogs, graphs, contexts, packages, and receipts are generated from reviewed authority rather than maintained manually in several places. Agent context is explicit Agents consume stable identifiers, statuses, provenance, relationships, and action boundaries instead of scraping visual components and inferring meaning from proximity. Creative freedom remains local The shared platform establishes trust and navigation without forcing every artifact into one template. Each child site keeps the visual system appropriate to its thesis. Operational surface stays small Static files reduce runtime dependencies, security exposure, platform administration, recovery complexity, and the number of places where truth can quietly diverge. A bounded architectural choice Why not build this review lab in SharePoint right now? Use SharePoint when Business teams need collaborative authoring, permissions, approvals, lists, forms, and Microsoft 365 integration. The content is enterprise knowledge whose canonical ownership belongs in SharePoint. Standard page components meet the experience requirement. Operational support and governance already exist for the site. Use this static prototype model when The goal is rapid high-fidelity exploration before selecting a production experience. Arbitrary HTML, calculators, local interaction, responsive systems, or agent surfaces must be preserved exactly. Byte identity, deterministic rebuilds, diff review, rollback, and machine-readable projections matter. The team needs a portable artifact that can be reviewed offline without tenant configuration or platform dependencies. This is not “SharePoint bad.” SharePoint remains a strong knowledge, permission, collaboration, and workflow plane. The argument is sequencing: prototype and prove the experience in a reversible static substrate first, then decide what should be implemented in SharePoint, a custom web experience, or a hybrid. Do not force early product discovery through the constraints of the eventual enterprise platform. Integrity inventory Source identities. Prototype Round Bytes SHA-256 Lifecycle Command Center 1 81,014 423252e62c670524f0f76cfea99bff1d4edf2e6476235fa02b85594e51b303e7 Service Atlas 1 79,743 b1e3eb351f48958d62ec49f02bf9e9fe3f31aa2011a7bd173b7450a0f5672d5c Engineering Confidence System 1 79,344 f26d6fee4cc8f347f31bd72495d1f6fe6074c5d5a5a6143c0346b2c246fc5b0d Operational Broadsheet 2 82,327 e7882274c4bc59060778713c75c0d1b3438c2ca940a5312ba07616d292e9f890 Engineering Blueprint 2 83,419 71369c6efcd6a3e75ff5ff56b28aa4a0cb1b3b39aff9f4192ce7de36587f9c8e Service Field Manual 2 83,734 e68005269aeaf6de01132123699e0c429ecd811f788a15984f021dee2c414e22 Context Ledger 3 146,393 84ea9f829668df26b02020604895bb2ffa0c4bad3b14ad995df3bd820b0f7ab7 Authority Weave 3 148,178 2979aac500c3167e91620ce327699969e222efe019f02f5247ff61357fab55ff Briefing Compiler 3 150,322 e096934ad38ac25cf09529af66f82047c7f6c31326070479fc4b1c733c3e12f1 Concept prototype. The artifact demonstrates nine generalized, synthetic, nonproduction site concepts. It does not publish employer data, controlled documents, production routes, authoritative prices, service commitments, or measured universal development-speed claims. Artifact record Nine Complete Enterprise Sites, One AI Prototyping Lab Metadata JSON Receipt Graph Publication Author Tony Malott Published July 14, 2026 Format Interactive Demonstration Privacy public-safe-synthetic JavaScript artifact-local Provenance owner-directed-ai-assisted-prototype-demonstration Only generalized synthetic prototypes and their deterministic evidence are published. No employer identity, controlled content, production route, authoritative price, or service commitment is included. Public sources 1 OT Endpoint Engineering prototype corpus nine byte-preserved child sites and parent review artifact Open source Related work 1 Architecture Review Plane: Three Interactive Product Concepts Three interactive, dependency-free Architecture Review Plane product concepts. Open artifact Share or reuse Send the page or take its public context with you. What’s included The agent package contains the canonical public HTML, public metadata, receipt, plain-text context, package guide, and member-hash manifest. Agent context is a generated public-safe plain-text projection. It is not canonical Markdown and does not replace the artifact or its versioned authority. SOURCE REFERENCES OT Endpoint Engineering prototype corpus package:shareplane-prototype-lab-v01.zip#sha256=ebde637712e1aad980a8774bee2ab40287a21803d75abba3ede7af567c7a8c5c