Before the Component

Independent public study · fictional scenarios

Before a component is chosen, what has already been decided?

Public Hawkins material describes how reusable components are created and maintained. This prototype asks what a layer above that public component lifecycle could look like: how purpose, content, and context determine which system response belongs—and when the system should defer to its community.

Follow a decision See the public basis

Not Netflix guidance. No internal access. The taxonomy and rules below are prototype proposals.

Three questions to carry with you

  1. 01 What must this moment help someone do?
  2. 02 What language belongs to the shared system?
  3. 03 What knowledge must remain with a domain or human owner?

The missing frame

A design system can tell you how a component works. It cannot decide why this is the right response.

This framework places an experience contract above the component library. It names the job, the content obligations, the relevant context, and who has authority. Only then does it assemble design and language together.

Purpose

The job this moment must do

Content

The meaning that must survive

Context

Audience, surface, state, risk

Authority

Who may decide, extend, or stop

Experience contract purpose × content × context × authority
One governed response

Component · copy · behavior · accessibility · reasons · receipt

The route is part of the artifact, not an explanation added afterward.

01

The shared system owns obligations

Required meaning, supported structures, exact constraints, and the minimum accessible behavior.

02

Domains extend without erasing the base

A domain can add a kind or vocabulary inside declared boundaries. It cannot quietly loosen the shared rules.

03

People retain judgment

High-risk or ambiguous decisions stop at a visible review boundary. A human decision is recorded; it does not rewrite the check.

Working proof

Give the same system three different situations. Watch what changes—and what refuses to.

The first decision establishes exact law. The next two show the thesis: a human boundary and a domain-owned extension. Every route leaves a verifiable receipt.

System response

One component, language, and behavior contract

Why this response

    Who decided what

    Inspect the portable receipt 
    
            
    
          
    
        
    
      
    

      
    
        
    
          
    A deliberately small taxonomy
    
          
    Kinds describe the job. Components remain candidates until the contract is satisfied.
    
          
    Three kinds are enough to prove three different ownership shapes: shared law, human review, and a domain extension.
    
        
    

        
    
          
    
            KindPurposeRoute requiresCandidate response
          
    
          
    
            discovery.collection_rowHelp people scan a meaningful setCollection goal · available items · low riskLabeled content row
          
    
          
    
            decision.destructive_confirmationMake an irreversible choice legibleDestructive state · named object · risk ownerAlert dialog + human gate
          
    
          
    
            recovery.blocking_interruptionRestore progress after a blocking breakKnown state · valid recovery action · domain authorityStatus notice + action
          
    
        
    
      
    

      
    
        
    
          
    Authority is data
    
          
    A rule cannot become law because it appeared in a public screenshot—or because an AI said so.
    
          
    Every finding carries its authority. Public observations can inform. Prototype adoptions can enforce. Domain extensions work only inside their declared scope. Human gates stop the system where judgment still belongs to people.
    
        
    
        
    
          
    Public observationEvidence only · never changes status
    
          
    Adopted for this prototypeExact, executable demo rule
    
          
    Extension adoptionExecutable only in its declared domain
    
          
    Human requiredVisible review boundary
    
        
    
      
    

      
    
        
    
          
    Pull it and use it
    
          
    The study is the interface. The contract underneath is the handoff.
    
          
    Clone it, run the same scenarios offline, alter a rule or extension, and watch the receipt change. No API key, model, package install, or network request is required.
    
        
    
        
    
          
    git clone https://github.com/calebstacy/before-the-component.git
cd before-the-component
npm test
npm start
    
          
    
            
    The browser and command line call the same evaluator.
    
            
    An agent can consume that evaluator over the included local protocol server and receive the same response, findings, and hashes.
    
            
    Open the repository
    
          
    
        
    
      
    

      
    
        
    
          
    Public basis
    
          
    What is observed, what is proposed
    
          
    The framework is original. Public sources establish the problem space, not the rules in the prototype.
    
        
    
        
      
          
    1. 
            Public Hawkins practitioner case study
            Used to understand the publicly described component lifecycle.
          
      2. 
          
    2. 
            DesignMD Netflix reference
            Third-party, reverse-engineered design observation. Only the downloaded reference frontmatter is recorded.
          
      3. 
          
    3. 
            Staff Systems Designer, Language posting
            Used as a public statement of the role’s systems-language problem.
          
      4.