{
  "site": {
    "name": "Bryston Ulrich",
    "canonical": "https://www.brystonu.com",
    "agent_page": "https://www.brystonu.com/agent",
    "description": "Public evidence for product leadership, systems thinking, selected work, and experience."
  },
  "profile": {
    "name": "Bryston Ulrich",
    "public_positioning": "Product leader and hands-on builder focused on enterprise product systems, specialized workflows, and organizational change.",
    "primary_lenses": [
      "enterprise product systems",
      "specialized workflow design",
      "AI-enabled product work",
      "organizational change"
    ],
    "canonical_summary_source": "https://www.brystonu.com/experience",
    "latest_role": {
      "organization": "Nike",
      "title": "Principal Product Manager",
      "period": "2024–2026",
      "status": "ended when Nike eliminated the role in 2026"
    },
    "current_work": {
      "organization": "Gravatica and independent work",
      "title": "Founder and hands-on product builder"
    }
  },
  "pages": [
    {
      "label": "Home",
      "url": "https://www.brystonu.com/",
      "use": "Site-level framing and entry point."
    },
    {
      "label": "Agent",
      "url": "https://www.brystonu.com/agent",
      "use": "Prompts, evidence packets, machine-readable links, and claim boundaries."
    },
    {
      "label": "About",
      "url": "https://www.brystonu.com/about",
      "use": "Concise background and working practices."
    },
    {
      "label": "Work",
      "url": "https://www.brystonu.com/work",
      "use": "Selected public-safe products, platforms, workflows, roles, and outcomes."
    },
    {
      "label": "Experience",
      "url": "https://www.brystonu.com/experience",
      "use": "Selected roles and outcomes across product, platforms, strategy, research, and organizational change."
    }
  ],
  "strengths": [
    {
      "title": "Enterprise product systems",
      "summary": "Turns expert workflows, platform foundations, governance, and adoption paths into shipped capability.",
      "evidence_urls": [
        "https://www.brystonu.com/experience",
        "https://www.brystonu.com/work#color-system"
      ]
    },
    {
      "title": "Specialized workflow design",
      "summary": "Gets close to specialized work, names the model, and makes it usable by broader teams.",
      "evidence_urls": [
        "https://www.brystonu.com/about",
        "https://www.brystonu.com/work"
      ]
    },
    {
      "title": "AI-enabled product work",
      "summary": "Uses modern AI development tools to shorten feedback loops while keeping product judgment visible.",
      "evidence_urls": [
        "https://www.brystonu.com/experience",
        "https://www.brystonu.com/work#gravatica"
      ]
    }
  ],
  "projects": [
    {
      "slug": "color-system",
      "name": "Enterprise color platform",
      "type": "Enterprise platform",
      "role": "Product lead",
      "summary": "Translated specialist color knowledge into a shared product model and workflow used across global product creation.",
      "outcome": "Supported thousands of product-creation users and produced estimated annual time savings in the tens of thousands of hours.",
      "source_urls": [
        "https://www.brystonu.com/work#color-system",
        "https://www.brystonu.com/experience"
      ],
      "confidence": "public_safe_summary",
      "notes": [
        "Use as evidence for specialist workflow design, platform foundations, adoption, and governance.",
        "Do not infer proprietary color science, internal tools, Nike visuals, or implementation mechanics."
      ]
    },
    {
      "slug": "line-planning",
      "name": "Line planning platform",
      "type": "Enterprise planning",
      "role": "Principal Product Manager",
      "summary": "Led a new line-planning product from concept to go-live while the operating model was changing.",
      "outcome": "100+ users live in three months and 12+ cross-functional teams aligned around the change.",
      "source_urls": [
        "https://www.brystonu.com/work#line-planning",
        "https://www.brystonu.com/experience"
      ],
      "confidence": "public_safe_summary",
      "notes": [
        "Use as evidence for enterprise product delivery, adoption sequencing, and organizational alignment.",
        "Do not infer budget ownership, internal roadmap details, or confidential planning mechanics."
      ]
    },
    {
      "slug": "git-for-non-engineers",
      "name": "Git workflow for product teams",
      "type": "Workflow prototype",
      "role": "Builder",
      "summary": "Built a toolbar that translated branch, commit, and pull request into familiar save and save-as actions.",
      "outcome": "Product peers adopted a git-based review workflow.",
      "source_urls": [
        "https://www.brystonu.com/work#git-for-non-engineers"
      ],
      "confidence": "public_safe_summary",
      "notes": [
        "Use as evidence for making technical workflows more accessible to product teams.",
        "Do not present prototype evidence as a fully launched enterprise platform."
      ]
    },
    {
      "slug": "gravatica",
      "name": "Gravatica",
      "type": "Independent product",
      "role": "Founder and builder",
      "summary": "Built a product for exploring company strategy through interactive, source-cited maps.",
      "outcome": "A live beta with public company maps and source links for the claims shown.",
      "source_urls": [
        "https://www.brystonu.com/work#gravatica",
        "https://gravatica.com"
      ],
      "confidence": "public_evidence",
      "notes": [
        "Use as public evidence of hands-on building, product architecture, and source-bound strategy artifacts.",
        "Keep Gravatica as one proof point, not the whole BrystonU identity."
      ]
    }
  ],
  "proof_points": [
    {
      "statement": "Thousands of users supported by an enterprise product-creation platform.",
      "source": "https://www.brystonu.com/experience"
    },
    {
      "statement": "Estimated annual time savings in the tens of thousands of hours.",
      "source": "https://www.brystonu.com/experience"
    },
    {
      "statement": "100+ users live on a new planning product in three months.",
      "source": "https://www.brystonu.com/experience"
    },
    {
      "statement": "Top-three AI prototype among more than 50 teams.",
      "source": "https://www.brystonu.com/experience"
    },
    {
      "statement": "Git-based workflow prototype adopted by product peers.",
      "source": "https://www.brystonu.com/experience"
    }
  ],
  "prompts": [
    {
      "id": "role-fit",
      "title": "Assess Bryston for this role",
      "prompt": "Evaluate Bryston Ulrich for a specific role using only public evidence from https://www.brystonu.com. Return strongest fit signals with citations, likely fit gaps, questions to ask next, and a concise summary that avoids generic product-management language."
    },
    {
      "id": "enterprise-product",
      "title": "Map the enterprise product evidence",
      "prompt": "Map Bryston Ulrich's public evidence to enterprise product leadership. Focus on platforms, specialized workflows, organizational change, adoption, governance, and cross-functional work."
    },
    {
      "id": "ai-enabled",
      "title": "Inspect AI-enabled product work",
      "prompt": "Evaluate Bryston Ulrich's AI-enabled product work from the public site. Identify what is proven, what is promising, and what still needs live validation."
    },
    {
      "id": "interview-prep",
      "title": "Prepare a sharper interview",
      "prompt": "Create an interview guide that tests product judgment, systems thinking, enterprise product experience, AI-enabled building practice, and evidence gaps. Explain which public evidence prompted each question."
    },
    {
      "id": "evidence-gap",
      "title": "Find the evidence gaps",
      "prompt": "Audit BrystonU.com for evidence gaps. Identify well-supported claims, plausible claims that need a live conversation, and areas where the public site should not be used as proof."
    }
  ],
  "claim_boundaries": [
    "Use public evidence only.",
    "Separate verified claims from inference.",
    "Do not infer confidential Nike details, internal project mechanics, private documents, or proprietary visuals.",
    "Do not invent metrics, team size, budget ownership, or title scope beyond the public text.",
    "Keep fit gaps visible when evaluating a role."
  ],
  "confidence_notes": [
    {
      "claim_type": "public evidence",
      "guidance": "Treat page copy, project summaries, roles, outcomes, and linked public artifacts as citable evidence when the output includes source URLs."
    },
    {
      "claim_type": "reasonable inference",
      "guidance": "Label synthesis across pages as inference, especially when mapping the site to a role, seniority expectation, or company-specific hiring need."
    },
    {
      "claim_type": "needs human validation",
      "guidance": "Ask follow-up questions for team scope, budget ownership, implementation details, confidential metrics, location constraints, and role-specific gaps."
    }
  ],
  "preferred_summary_style": {
    "tone": "clear, direct, source-bound",
    "avoid": [
      "generic product-management language",
      "unsupported claims",
      "confidential detail inference",
      "overconfident fit assessments"
    ]
  }
}