Skip to main content

Builder33

Explanation page. This page states the Builder33 path from a perspective to a deployment.

The source is architecture_plan/builder33.md. That file names six stages and one flow.

Scope​

Every statement on this page comes from architecture_plan/builder33.md. This page does not change that file.

The notes do not give a Builder33 version. The notes do not list the fields in "other metadata".

This page does not specify storage, APIs, or hooks. This page does not describe Agentic behavior.

Prerequisites​

The reader needs the stage names in architecture_plan/builder33.md. The reader does not need a running system.

Thesis​

The notes order the path as perspective, template, renderer, compiler, and deployment.

Mental model​

The design system holds design components and the metadata needed to generate perspectives. The extractor generates templates from each design component and each perspective. Context Flow Programming is the definition of visual elements and code. The renderer generates code from Context Flow Programming and the perspectives. The compiler compiles that code into an application. Deploy deploys the code.

PartRole in the notes
Design systemHolds design components and the metadata needed to generate perspectives
PerspectiveName, description, version, prompt, and other metadata
ExtractorGenerates templates from each design component and each perspective
TemplateCode samples, prompts, validation, demo displays, and sample data
Context Flow ProgrammingDefinition of visual elements and code
RendererGenerates code from Context Flow Programming and the perspectives
CompilerCompiles the code into an application
DeployDeploys the code
AgenticHeading only. The notes give no statements

The notes draw this flow:

perspective --> template --> renderer --> compiler --> deployment

Causal detail​

Design system​

The design system holds design components. It holds the metadata needed to generate perspectives. The notes put a name, a description, a version, other metadata, and multiple perspectives in that same container. The notes do not say which of those items sit on the design system. The notes do not say which of those items sit on a design component.

Perspective​

Each perspective has a name, a description, a version, a prompt, and other metadata. The prompt belongs to the perspective. The notes do not give a prompt to the design system container.

Extractor​

The extractor generates templates. It uses each defined design component and each perspective. A template contains code samples, prompts, validation, demo displays, and sample data.

Context Flow Programming​

Context Flow Programming is the definition of visual elements and code. The notes name form layout, schema, relationships between components, and end components. The notes put "like" before that list. The notes do not say that the list is complete.

Renderer​

The renderer generates code from Context Flow Programming and the perspectives. The renderer sentence in the notes does not name the template.

Compiler​

The compiler compiles the code into an application.

Deploy​

Deploy deploys the code. The flow names the last step deployment. The notes do not say that Deploy reads the application.

Flow and the stage sentences​

The flow starts at perspective. The flow does not start at the design system. The flow includes the template. The renderer sentence does not include the template. The renderer sentence includes Context Flow Programming. The flow does not include Context Flow Programming. This page keeps both statements.

Tradeoffs​

The notes record one flow. The notes do not record a second flow. The notes do not record a rejected stage.

Boundaries​

  • The Agentic heading has no sentences under it.
  • "Other metadata" has no field names.
  • The notes do not split design-system fields from design-component fields.
  • The template is in the flow and absent from the renderer sentence.
  • Context Flow Programming is in the renderer sentence and absent from the flow.
  • The compiler output is an application. The Deploy sentence names the code.
  • The notes do not link Context Flow Programming to docs/cfp/.
  • The notes do not link Builder33 to the Logic Bee Builder.

Verification​

architecture_plan/builder33.md has six stage headings, a Flow heading, and an Agentic heading. This page uses those headings, the perspective fields, the template contents, and the flow line. The Agentic heading has no body in the notes.

Recovery​

If this page names a behavior that architecture_plan/builder33.md does not name, delete that behavior from this page. If Agentic remains only a heading, leave Agentic undefined.

The source notes are architecture_plan/builder33.md.