Processing Core

Context Builders

Builder governance should read like scoped capability review, not like a raw registry dump.

Builder Registry

See builder coverage first. Open raw definition detail only when you need it.

Context builders define trigger coverage, analysis boundaries, upstream sources, and downstream outputs. This page now treats audit gaps as the primary signal.

Optional service token

Builders

registered

Missing audit

needs review

Missing trigger coverage

audit gaps

Missing output mapping

runtime risk

Builder Registry

Select a builder to inspect its active definition and audit posture.

No context builders yet

When builder definitions exist, they will appear here as selectable capability cards.

Audit Findings

Missing trigger coverage, source coverage, and output mapping gaps are surfaced as readable findings instead of raw rows.

No audit findings

Builder audit is currently clean.

Builder Detail

Selected builder detail starts with scope, runtime state, and governance posture. The authored structure stays available as an advanced layer.

No builder selected

Choose a builder from the left to inspect its active version.

Create Builder Draft

Create a builder with guided fields first. Advanced structure editing stays behind an explicit detail foldout.

Builder key

Use a stable machine key that reflects the builder's purpose.

Display name

Use the human-facing name reviewers should see in the workspace.

Scope

Choose the core object or process area this builder shapes.

Draft builder structure

Open this when you need to author trigger conditions, analysis boundaries, inputs, or outputs directly.

Current draft builder summary

Trigger Conditions

None

Analysis Boundaries

None

Upstream Sources

objects, relationship_edges, events

Downstream Outputs

None

Linked Dictionary Keys

None

Audit Status

draft

Show draft builder structure