Growth Architecture OS

Jared Silverman's public operating system for growth leadership.

This repository is not a portfolio in the usual sense. It is a structured view of how I think, operate, diagnose growth systems, build decision infrastructure, and turn fragmented marketing environments into something leaders can actually manage.

My work sits at the intersection of performance media, CRO, analytics, marketing operations, agency governance, and AI-enabled workflows. The throughline is simple: stabilize the system, then scale it.

Five-minute proof

Do not read the repository front to back. Start with the question you are trying to answer.

Question	Evidence
Can I run a complex growth system?	02-growth-architecture/performance-media-operating-model.md
Can I connect media performance to business economics without overstating causality?	06-reference/media-metrics-to-financial-outcomes.md
Can I show bounded evidence?	See the two carefully scoped case studies below.
Can I establish an operating rhythm quickly?	03-playbooks/first-90-days.md
Is the AI work governed and useful?	04-ai-systems/ai-operating-model.md

Bounded evidence

Case study	Bounded evidence
App Growth Rebuild	Approved applications grew ~500% after the rebuild; application-stage only
Education Performance Media Rebuild	Directional cost-per-enrollment, approved-application efficiency, and portfolio pacing improvements

What this repo is

Growth usually does not break because a team lacks tactics. It breaks because the operating model is unclear: spend moves faster than measurement, agencies execute without a shared standard, teams debate reports instead of decisions, and leadership sees risk too late.

This repo documents the system I use to solve that problem.

Core point of view

I build the operating system underneath growth: the visibility, standards, QA, cadence, and decision logic that make spend easier to manage and performance easier to improve.

flowchart TD
    A[Messy growth environment] --> B[Diagnostic lenses]
    B --> C[Operating system layer]
    C --> D[Playbooks and templates]
    C --> E[Data dictionaries and taxonomy]
    C --> F[AI-enabled workflows]
    C --> G[Governance and decision cadence]
    D --> H[Clearer execution]
    E --> H
    F --> H
    G --> H
    H --> I[More visible, governable, repeatable growth]

Loading

Ecosystem map

Growth Architecture OS is the center of the public portfolio. The supporting repos show how specific parts of the operating system become reusable tools, playbooks, context systems, and implementation layers.

The private-to-public-release-gate adds the publication-governance layer: it demonstrates how private canonical work can produce a reviewed public artifact through explicit exclusions, privacy scanning, allowlisted overlays, and Git-aware drift checks.

For the canonical portfolio map and supporting navigation, see docs/ecosystem-map.md.

flowchart TD
    OS[Growth Architecture OS] --> MI[Marketing Intelligence Agent]
    OS --> Toolkit[Marketing Ops Toolkit]
    OS --> Playbooks[Marketing Ops Playbooks]
    OS --> Context[Brand Context System]
    Context --> Starter[Brand Design System Starter]
    OS --> Starter

    MI --> Briefs[Monitoring and executive briefs]
    Toolkit --> Automation[Operational scripts]
    Playbooks --> Repeatable[Repeatable governance methods]
    Context --> Inputs[Structured context bundle]
    Starter --> Tokens[Tokens, foundations, components]

Loading

Repo map

Folder / File	Purpose
00-positioning/	Executive narrative, bio, leadership principles, operating style, proof controls
01-case-studies/	Public-safe case studies from growth, CRO, media, and operating-model work
02-growth-architecture/	Reusable frameworks for media, CRO, reporting, and agency governance
03-playbooks/	Practical playbooks for diagnosis, triage, testing, taxonomy, and media correction
04-ai-systems/	AI-enabled marketing operations, agent workflows, prompt patterns, and risk controls
05-templates/	Executive-ready templates and meeting guides
06-reference/	Small reference models for signal quality, outcome logic, financial translation, and decision support
07-data-dictionaries/	Shared KPI, funnel, taxonomy, and reporting language
08-brand-and-voice/	Writing style, personal brand system, and communication rules
09-positioning/	Private positioning material for role targeting, interview stories, and recruiter conversations
10-thought-leadership/	Public POV files from articles, platform shifts, and media strategy themes
_meta/	Content map, source index, and repo metadata
design-system/	Lightweight visual/token system for future web or portfolio work; intentionally in progress
docs/	Longer thesis and explanatory articles behind the operating system
GOVERNANCE.md	Public governance standard for claim discipline, source support, and public safety
proof-points.md	Root alias for the canonical claim bank in 00-positioning/

Related repos

This repo is part of a connected public system. See the GitHub Ecosystem Map for how the repos relate.

• marketing-intelligence-agent
• marketing-ops-toolkit
• marketing-ops-playbooks
• brand-context-system
• brand-design-system-starter

Signature frameworks

The first 90 days

1. Days 1-30: Listen hard. Map reality. Find the leaks.
2. Days 31-60: Rebuild the layer that makes execution trustworthy.
3. Days 61-90: Move from recovery mode to operating rhythm.

By day 90, leadership should know what is working, what is risky, who owns what, and where to invest next.

Five diagnostic lenses

1. Demand reality
2. Measurement integrity
3. Media allocation
4. Agency and team model
5. Leadership cadence

Operating pillars

• Operating discipline
• Visibility that drives action
• Governance that improves performance
• Decision-ready communication
• Reusable operating models

How to read this repo

For a narrative on how this GitHub ecosystem fits together, see docs/why-i-run-growth-like-a-platform-team.md. For a concise repo-by-repo map, see docs/ecosystem-map.md. For shared terminology, see docs/common-language.md. For role-specific reader paths, see docs/evaluator-paths.md. For finance-first evaluators, see 06-reference/media-metrics-to-financial-outcomes.md.

Use the five-minute proof above for a fast inspection, or docs/evaluator-paths.md for a role-specific route. The repository is meant to show the work behind the resume, not make you take the resume's claims on faith.

Further reading

• Why I Run Growth Like a Platform Team
• GitHub Ecosystem Map
• Common Language
• Evaluator Paths
• Media Metrics to Financial Outcomes

Review standard

The repo should not sound more certain than the source material. Metrics, titles, case studies, and public-facing summaries should stay grounded in resume, portfolio, deck, article, or source-note support.

IP and usage

This repository contains Jared Silverman's personal intellectual property, professional positioning, frameworks, templates, and work samples. It is shared for evaluation, collaboration, and professional context. It is not licensed for reuse, resale, training, or commercial adaptation without permission.

Usage and rights: see USAGE.md.

© 2026 Jared Silverman. All rights reserved.