Skip to content

docs: clarify artifact lifecycle stages - #31

Merged
ElvinMorales merged 1 commit into
mainfrom
docs/artifact-lifecycle-stage-polish
Jun 17, 2026
Merged

docs: clarify artifact lifecycle stages#31
ElvinMorales merged 1 commit into
mainfrom
docs/artifact-lifecycle-stage-polish

Conversation

@ElvinMorales

Copy link
Copy Markdown
Owner

Summary

This PR closes the artifact lifecycle documentation gap by making lifecycle stages explicit across the builder.

It adds controlled lifecycle-stage documentation, updates catalog metadata, shows lifecycle stage information in the learning panel, and adds runtime public-safety guidance for runtime artifacts.

Issue addressed

Closes #4

Changes

  • Adds docs/artifact-lifecycle.md

  • Defines the controlled lifecycle stages:

    • design-time
    • runtime
    • iteration
  • Updates src/data/artifactCatalog.js so all artifacts use the controlled lifecycle vocabulary

  • Remaps prior build-time artifacts to design-time

  • Remaps eval-rubric to iteration

  • Adds runtime public-safety guidance to runtime artifacts

  • Updates the learning panel to show:

    • formatted lifecycle stage
    • short lifecycle explanation
    • runtime warning where applicable
  • Updates related docs:

    • README
    • taxonomy alignment
    • rendering strategy
    • catalog renderer coverage
    • public-safety checklist
    • synthetic example README
  • Updates tests to enforce lifecycle metadata and runtime safety guidance

Boundary decisions

  • Design-time artifacts define agent structure, policies, prompts, schemas, and reusable templates.
  • Runtime artifacts describe execution posture or configuration, but public repos should not include unsanitized live runtime data.
  • Iteration artifacts capture versioning, feedback, evaluation results, release notes, and improvement loops.
  • Memory and state remain separate.
  • State is not durable memory.
  • Protocol surfaces remain mappings/adapters, not taxonomy replacements.

Validation

  • git status --short --branch

  • git diff --check

  • node --check src/app.js

  • node --check src/renderers/markdownRenderer.js

  • node --check src/renderers/artifactRenderers.js

  • node --check src/renderers/rendererUtils.js

  • node --check src/examples/exampleValues.js

  • node --check src/data/artifactCatalog.js

  • node tests/catalogIntegrity.test.mjs

  • node tests/rendererSmoke.test.mjs

  • Static server returned HTTP 200 for:

    • /
    • app.js
    • data/artifactCatalog.js

Known limitations

Browser click-through validation was not completed because the in-app browser target was unavailable in the Codex session.

The temporary local server was stopped.

@ElvinMorales
ElvinMorales merged commit b64ecac into main Jun 17, 2026
1 check passed
@ElvinMorales
ElvinMorales deleted the docs/artifact-lifecycle-stage-polish branch June 17, 2026 22:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[G2: Taxonomy data] Document artifact stages: design-time, runtime, and iteration

1 participant