Forge Intelligence

Creation and Artifact Realization Intelligence

Transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.

Updated

Definition

Transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.

Coverage role

Separates idea generation from the disciplined work of making something real. It is reusable across software, documents, services, processes, products, media, organizations, and other specialist domains.

Scope

Included

  • creation brief interpretation
  • requirements and acceptance criteria
  • medium and method selection
  • artifact architecture
  • prototype and progressive fidelity
  • implementation and integration
  • revision and configuration control
  • acceptance and packaging
  • handoff and maintenance intent

Excluded and non-goals

  • claiming an artifact was built when only a description exists
  • skipping specialist competence
  • performing irreversible actions without approval
  • ignoring accessibility safety provenance or licensing
  • treating generated output as validated
  • autonomously publishing purchasing submitting or deploying

Boundary rules

  • Route to general.creation-realization when the requested outcome requires one or more declared capabilities and the output can be represented by its canonical artifacts.
  • Route to an adjacent or specialist intelligence when domain-specific rules, tools, or professional authority dominate the problem.
  • Use general.reasoning to coordinate multi-pack conflicts, hard constraints, uncertainty, and decision status.
  • Return ask, defer, or escalate when required context, source authority, consent, or accountable ownership is missing.

Capability semantics

Capability ID Name Semantic intent
capability.general.creation-realization.interpret_creation_brief Interpret Creation Brief Translate intent, audience, context, constraints, source material, risks, and non-goals into a controlled creation brief.
capability.general.creation-realization.derive_requirements_and_acceptance Derive Requirements And Acceptance Create testable functional, quality, accessibility, provenance, safety, and handoff criteria.
capability.general.creation-realization.select_medium_method_and_tools Select Medium Method And Tools Choose an appropriate representation, process, toolchain, degree of automation, and specialist involvement.
capability.general.creation-realization.architect_artifact Architect Artifact Define modules, structure, interfaces, dependencies, content model, configuration, and integration plan.
capability.general.creation-realization.prototype_progressively Prototype Progressively Produce low-cost reversible prototypes before high-cost or irreversible realization.
capability.general.creation-realization.implement_and_integrate Implement And Integrate Create components, preserve provenance, integrate them, and record deviations from the approved design.
capability.general.creation-realization.revise_from_feedback Revise From Feedback Classify feedback, repair defects, manage scope changes, compare versions, and preserve rejected alternatives.
capability.general.creation-realization.verify_accept_and_package Verify Accept And Package Run declared validators, obtain required human acceptance, package the artifact, and mark residual limitations.
capability.general.creation-realization.handoff_and_define_lifecycle Handoff And Define Lifecycle Provide ownership, operating instructions, maintenance expectations, versioning, rollback, and review triggers.

Canonical artifact concepts

Artifact type Structural category Semantic purpose
artifact.general.creation-realization.creation_brief brief Creation Brief for Creation and Artifact Realization Intelligence: A bounded specification of purpose, stakeholders, requirements, constraints, assumptions, and success criteria. It supports the pack purpose of transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.
artifact.general.creation-realization.requirements_and_acceptance_matrix acceptance_contract Requirements And Acceptance Matrix for Creation and Artifact Realization Intelligence: A traceable requirement and acceptance contract linking each obligation to an observable criterion, verifier, owner, and status. It supports the pack purpose of transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.
artifact.general.creation-realization.method_and_tool_decision decision Method And Tool Decision for Creation and Artifact Realization Intelligence: A bounded decision or routing record that exposes alternatives, governing constraints, evidence, rationale, ownership, status, and reopening conditions. It supports the pack purpose of transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.
artifact.general.creation-realization.artifact_architecture model Artifact Architecture for Creation and Artifact Realization Intelligence: A purpose-bounded representation of entities, relationships, assumptions, boundaries, and evidence of adequacy. It supports the pack purpose of transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.
artifact.general.creation-realization.prototype_set portfolio Prototype Set for Creation and Artifact Realization Intelligence: A deliberately varied set of candidates with lineage, constraints, screening state, and selection rationale. It supports the pack purpose of transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.
artifact.general.creation-realization.realized_artifact structured_output Realized Artifact for Creation and Artifact Realization Intelligence: A typed domain output that preserves purpose, context, evidence, assumptions, status, and next action. It supports the pack purpose of transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.
artifact.general.creation-realization.integration_and_revision_log ledger Integration And Revision Log for Creation and Artifact Realization Intelligence: A controlled collection of uniquely identified entries with ownership, provenance, status, and review state. It supports the pack purpose of transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.
artifact.general.creation-realization.acceptance_report acceptance_contract Acceptance Report for Creation and Artifact Realization Intelligence: A traceable requirement and acceptance contract linking each obligation to an observable criterion, verifier, owner, and status. It supports the pack purpose of transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.
artifact.general.creation-realization.handoff_and_lifecycle_package evidence_package Handoff And Lifecycle Package for Creation and Artifact Realization Intelligence: A versioned evidence package with indexed contents, completeness state, recipient, approval, submission, retention, and revision controls. It supports the pack purpose of transform an approved intent or concept into a coherent, usable, traceable artifact through requirements, architecture, prototyping, implementation, integration, revision, acceptance, and handoff.

Method families and limits

Method ID Method Use when Avoid when
method.general.creation-realization.brief_to_artifact_traceability brief-to-artifact traceability Use when an ambiguous request must be converted into a decision-relevant, answerable, bounded question or requirements brief. Avoid endless clarification, leading questions, hidden presuppositions, unnecessary personal-data collection, and solutioning before the decision context is known.
method.general.creation-realization.progressive_fidelity progressive fidelity Use when an artifact must move from intent through architecture, prototype, implementation, review, release, and maintainable handoff. Avoid irreversible high-fidelity work before requirements are testable, undocumented configuration drift, unreviewed external release, or change without rollback.
method.general.creation-realization.modular_and_interface_first_design modular and interface-first design Use when an artifact must move from intent through architecture, prototype, implementation, review, release, and maintainable handoff. Avoid irreversible high-fidelity work before requirements are testable, undocumented configuration drift, unreviewed external release, or change without rollback.
method.general.creation-realization.iterative_critique_and_revision iterative critique and revision Use when an artifact must move from intent through architecture, prototype, implementation, review, release, and maintainable handoff. Avoid irreversible high-fidelity work before requirements are testable, undocumented configuration drift, unreviewed external release, or change without rollback.
method.general.creation-realization.configuration_and_version_management configuration and version management Use when an artifact must move from intent through architecture, prototype, implementation, review, release, and maintainable handoff. Avoid irreversible high-fidelity work before requirements are testable, undocumented configuration drift, unreviewed external release, or change without rollback.
method.general.creation-realization.test_driven_or_acceptance_driven_creation test-driven or acceptance-driven creation Use when a claim, requirement, artifact, process, model, or system needs bounded evidence of conformance and fitness for intended use. Avoid self-certification by the generator alone, tests without traceability to claims, or a pass status that omits untested scope and residual risk.
method.general.creation-realization.design_for_accessibility_and_maintenance design for accessibility and maintenance Use when participation depends on interaction between a person, task, environment, interface, support, and changing context. Avoid assuming one impairment profile, choosing assistive options without the person, or treating minimum compliance as evidence of usable participation.
method.general.creation-realization.human_in_the_loop_approval human-in-the-loop approval Use when an artifact must move from intent through architecture, prototype, implementation, review, release, and maintainable handoff. Avoid irreversible high-fidelity work before requirements are testable, undocumented configuration drift, unreviewed external release, or change without rollback.
method.general.creation-realization.rollback_and_reversible_deployment rollback and reversible deployment Use when an artifact must move from intent through architecture, prototype, implementation, review, release, and maintainable handoff. Avoid irreversible high-fidelity work before requirements are testable, undocumented configuration drift, unreviewed external release, or change without rollback.

Pack-specific invariants

The pack also inherits the core invariants in core/core_invariants.yaml.

Invariant ID Statement Failure action
invariant.general.creation-realization.01_a_realized_artifact_traces_to_an_approved_brief_requiremen A realized artifact traces to an approved brief, requirements, and acceptance criteria. repair_or_conditional_pass
invariant.general.creation-realization.02_draft_prototype_candidate_accepted_and_deployed_states_are Draft prototype candidate accepted and deployed states are never conflated. repair_or_conditional_pass
invariant.general.creation-realization.03_irreversible_or_externally_consequential_actions_require_a Irreversible or externally consequential actions require an explicit authority gate. repair_or_conditional_pass
invariant.general.creation-realization.04_provenance_licenses_source_transformations_and_generated_c Provenance licenses source transformations and generated components remain traceable. repair_or_conditional_pass
invariant.general.creation-realization.05_accessibility_safety_privacy_security_and_maintainability Accessibility safety privacy security and maintainability are treated as requirements when relevant. repair_or_conditional_pass
invariant.general.creation-realization.06_deviations_and_unresolved_defects_are_visible_in_the_hando Deviations and unresolved defects are visible in the handoff rather than hidden by completion language. repair_or_conditional_pass
invariant.general.creation-realization.07_the_final_artifact_is_independently_validated_according_to The final artifact is independently validated according to risk and is not accepted on generator self-assessment alone. repair_or_conditional_pass
invariant.general.creation-realization.08_ownership_maintenance_rollback_and_review_triggers_are_def Ownership maintenance rollback and review triggers are defined before operational use. repair_or_conditional_pass

Dependencies and relations

Operational general intelligences: general.question-framing, general.creativity, general.system-modeling-simulation, general.validation-verification
Foundation concepts: general.planning-execution, general.practical-procedural, general.tool-computational, general.communication-explanatory
Life intelligences: None

Source roles

Source ID Claim roles Runtime resolution required
iso.innovation_56007 concept_definition, interoperability_or_formal_contract False
nasa.systems_engineering concept_definition, engineering_method, verification_and_validation False
oecd.creative_thinking competence_framework, concept_definition, evaluation_dimension False
w3c.wcag concept_definition, interoperability_or_formal_contract False

Risk and authority boundary

Risk class: moderate

  • Creation includes publication deployment purchase submission physical fabrication or another consequential external action.
  • The artifact is safety-critical regulated security-sensitive or intended for professional reliance.
  • Ownership consent licensing confidentiality or authority to create is unresolved.

Accountable people retain consent, value, regulated, irreversible, and residual-risk decisions. This semantic page does not claim a deployed implementation.

Maturity

semantic: S3_reviewable_definition
contract: C3_testable_contract
implementation: I0_not_included
evidence: E2_source_roles_mapped
governance: G2_controls_and_review_defined
overlay: O2_paired_seed_complete

Paired overlay

Runtime maturity

  • Capabilities: 9
  • Technical floor→ceiling: I1_runtimeI1_runtime
  • Autonomy floor→ceiling: A0_assistedA0_assisted
  • I1_runtime count: 9
  • Evidence class: contract: 9
  • Full hierarchy: MATURITY-HIERARCHY.md

Evaluation suite status

  • CI status: pass
  • Suite: evaluation_suites/creation-realization.yaml
  • Cases defined: 7
  • Capabilities under test: 9