PROMPT SKETCH
Compose harness components only through compatible contracts. Reject an invalid composition before execution, and keep the builder and component versions immutable.Composable harness foundry
Construct and evolve reusable harness components.
JOIN POINT
harness_component_build_and_evaluateRECORD STATUSCandidate · v0.1.001
UML class view
The proposed contract drawn as participant roles, received calls, and numbered dependencies.
02
Object interactions
The same roles and calls as a class collaboration and a numbered message sequence.
03
Pointcut
Where the mechanism applies. All four dimensions belong to the proposed match, not just its vocabulary.
- Context
- Harness behavior is assembled from independently typed components.
- Trigger
- Components are selected, composed, or replaced.
- Structure
- Component interface, composition builder, evaluator, and artifact registry.
- Effect
- The built harness is executable and its component provenance is recoverable.
04
Protected contract
The obligation that clients, operators, and auditors should be able to rely on.
- Requires
- Components have compatible contracts and composition operators.
- Ensures
- Invalid composition is rejected before execution.
- Invariant
- Reusing a component does not silently reuse privileged state.
- Violation
- Build conflicts, incompatible versions, and evaluation failure are explicit.
Negative control
Separate helper functions without component contracts are insufficient.
05
Variation & lifecycle
The hot spot is admitted only where the protected semantics survive.
Permitted variation
Typed processors, foundry DSL, component search, and immutable builders.
Test obligation
Test composition, incompatible component, rebuild, and provenance.
Evolution question
Did composition move from code edits to a searchable component space?
06
Prompt + code design
An illustrative prompt and a small design sketch for the proposed contract. Names and APIs are invented; this is not a repository excerpt.
CODE DESIGN / PYTHON
def compose(components):
builder = HarnessBuilder()
for component in components:
if not builder.accepts(component.contract):
raise IncompatibleComposition(component.id, builder.contract)
builder = builder.add(component)
return builder.freeze()Illustrative design sketch. A foundry's value is rejection before execution, not a larger configuration space. This example is a teaching aid, not implementation evidence or a conformance claim.
07
Detection & matching
The frozen rule that retrieves this record, the canonical source exemplar, and the control that should stay unmatched.
- Join point
harness_component_build_and_evaluate- Source locator
- See the source record.
- Lexical cue
(?i)\b(?:harness[_-]?foundry|HarnessX|component[_-]?search|composable[_-]?harness)\bFrozen expression, v0.1.0. A match is a retrieval cue, not a confirmed implementation.- Aliases
- harnessfoundry, componentsearch, harnessbuild, composeharness
- Canonical exemplar
- Darwin-Agent/HarnessX
harnessx/core/builder.py:73Support: tests/unit/test_builder.py:1 - Negative control
- Separate helper functions without component contracts are insufficient.
Scope-anchored review. pohe-agent analyze <repo> --pattern E05 anchors the cue to its enclosing declaration and checks a separate operational signature for all four pointcut dimensions. Missing roles and negative-control risks remain visible; a structural match is not E2/E3. Calibration report ↗
08
Repository files
Up to five public files retrieved by the frozen cue and pinned to the audited commit. A match is a place to inspect, not a confirmed implementation.
09
Evidence & provenance
Each layer answers a different question. Do not substitute retrieval for review.
Source-located exemplar
A concrete source anchor is available for this proposed record. It is one exemplar, not evidence that all repositories—or every contract field—conform.
Review boundary: this candidate and its specification come from an AI-assisted study. Independent human validation remains open.
ANY-EVIDENCE FAMILY COVERAGE2/36
5.6% of repository families in the frozen panel have at least one current cue, historical cue, or canonical source layer. This is not confirmed prevalence.
Current lexical-cue repositories: 2 / 41Canonical source anchorDarwin-Agent/HarnessX
ccb411691343harnessx/core/builder.py:73Supporting surface
tests/unit/test_builder.py:1Immutable composition of typed harness processors.
Exploratory retrieval cue Regex / v0.1.0
(?i)\b(?:harness[_-]?foundry|HarnessX|component[_-]?search|composable[_-]?harness)\bThis expression is a discovery instrument only. A match is a retrieval cue—not a confirmed implementation, pointcut match, or contract proof.