Skip to main content
Have a synthetic signal to inspect? Open the offline inspector walkthrough.
Customer guide

UMBRIQ architecture under development

Understand the proposed consent, task-result and correction boundaries without treating a local baseline as a deployed service.

For: Data-rights owner, AI governance lead, Task reviewer

Before you begin

Before any customer-data learning, identify the exact source, purpose, rights holder and eligible task. Applicable terms require review and agreement, and customer learning requires explicit opt-in.

  1. Do not provide customer data or raw prompt archives to establish a task.
  2. Identify the owner who can withdraw or correct the source authorization.

Supported scope and current status

UMBRIQ currently has an executable local baseline, not a connected deployed result plane or a trained customer task. Its first-release signal is observational class/count and coverage, with no confidence, probability, span, tenant, policy or action authority.

  1. Treat a declared task or model as not run until current consumer evidence exists.
  2. Keep an observation separate from a policy decision.

Compare this path with the published coverage table and the coverage guide.

Set up the path

The planned customer workflow requires purpose-specific rights and separate task eligibility before any source is activated. A customer administrator would review the exact consent and recipient scope; no current public activation recipe is available.

  1. Ask for the current product and privacy terms for the specific task.
  2. Do not infer broad tenant permission from a single source consent.

Use the workflow

If a future release offers an approved task result, open the exact task and version, then review the signed result and typed degradation state. A correction or withdrawal is a new accountable action, not an edit to old history.

  1. Distinguish unknown, not run and input-limited states from a clean result.
  2. Request a correction against the exact source and result.

Verify the result

A future signed result must bind the trained model, runtime, rights and sequence to the exact task. A metadata card, sample output or passing local test is not proof that a customer consumer ran.

  1. Read back current task eligibility and result status.
  2. Confirm a withdrawn source is fenced from later use before treating deletion as complete.

Coverage references: 24 requirements, 0 currently passed

This guide is bound to 24 requirements in RedactWall's acceptance crosswalk, which is maintained internally and not published. A requirement counts as passed here only after current evidence for every bound scenario and authority has been published; none has been published yet.

See the public verification overview and the documentation coverage guide.

Denials and recovery

Missing rights, stale consent, absent labels or an unmeasured profile block activation. Do not turn an unavailable result into an allow decision or a reassuring zero.

  1. Record the exact blocking input without sharing source content.
  2. Retry only after an authorized owner supplies new rights and release proof.

For customer-side next steps, read Recovery and support.

Billing and integration handoffs

A future task may use a separate approved consumer and source connection. Neither a RedactWall workspace nor a paid device seat grants permission to pool, train on or export customer data.

  1. Review /privacy for the current learning-policy status.
  2. Confirm commercial and integration scope before any data handoff.

Limits to keep in view

Nine planned tasks remain blocked for customer activation pending task-specific privacy/legal approval, independent labels and signed measured numeric profiles. Synthetic-stage qualification would not authorize customer data.

  1. Do not describe local baseline behavior as a deployed task.
  2. Do not turn an observational signal into confidence, policy or action authority.

Review the current Disclosures before relying on a capability.

Inspect a contextual signal offline

Use umbriq-signal inspect to check one existing contextual-signal JSON document and read a structural summary. This command does not classify text. It does not authenticate the producer, verify freshness, make a policy decision or activate a customer task.

The walkthrough uses authorized source access to skellywix/RedactWall-UMBRIQ at revision a418fe85c8266966937f72c670d66e1fa4a10744. Source availability establishes no deployed service, public repository access, published binary download or package-registry release. The examples below use only the repository's synthetic fixtures.

1. Build with the existing toolchain

This walkthrough uses Windows, PowerShell 7 and Go 1.26.9. Start at the pinned checkout root with the required Go modules already cached. Replace <existing-owned-directory> in each command with the same absolute directory you own; use an output path that contains no binary you need to preserve. The build can replace that output file. It uses the local toolchain and refuses dependency downloads. If the cache is incomplete, stop and obtain the approved dependencies through your source-access process.

$env:GOTOOLCHAIN = 'local'
$env:GOPROXY = 'off'
$env:GOSUMDB = 'off'
go build -mod=readonly -o '<existing-owned-directory>/umbriq-signal.exe' ./cmd/umbriq-signal

Check $LASTEXITCODE immediately after the command. Continue only when it is 0. The build creates a local executable; it does not install or start a service.

2. Inspect a known synthetic signal

From the checkout root, pipe the positive fixture into the executable. The pipe closes standard input when the file ends. The executable also runs outside the checkout: supply the full path to your input file, or copy the fixture files with the same relative directory layout.

Get-Content -Raw -LiteralPath 'contracts/fixtures/contextual-signal/positive-complete-with-labels.json' |
  & '<existing-owned-directory>/umbriq-signal.exe' inspect

Expected result: exit 0, empty standard error, and this single JSON line on standard output:

{"inspection":"structural_only","signal_contract_version":"1.0.0","task_id":"contextual_data_classification_v1","task_spec_version":"1.1.0","coverage":"complete","label_count":1,"observation_count":1,"unrecognized_label_count":0}
Coverage
The input's validated coverage value. complete is not an independent assessment of protection.
Label and observation counts
label_count counts recognized label entries; observation_count sums their reported observations. unrecognized_label_count keeps the supplied unknown-label count separate.
Structural inspection
A valid document, including complete coverage with zero labels, is not proof that content is clean. The summary grants no release, policy or customer-data authority.

3. Recognize a refused input

This synthetic negative fixture carries a tenant field that the observational signal contract does not permit. Run it separately from the positive example:

Get-Content -Raw -LiteralPath 'contracts/fixtures/contextual-signal/negative-signal-carries-a-tenant.json' |
  & '<existing-owned-directory>/umbriq-signal.exe' inspect

Expected result: $LASTEXITCODE is 1, standard output is empty, and standard error is umbriq-signal: invalid contextual signal. Correct the producing document or use a compatible source revision, then inspect again. Do not replace a refusal with a clean result or strip fields from an authentic record merely to make it pass.

Input and recovery limits

Supply exactly one first-release contextual-signal JSON document, then close standard input. The inclusive limit is 2,097,152 bytes (2 MiB), including whitespace. A task request, signed result envelope or raw prompt is a different input. The command refuses malformed, duplicate, unknown, mismatched, oversized and trailing input; expected task version and vocabulary come from the compiled source. An exit of 1 can also mean an input/output failure, and 2 means invalid arguments. --help prints usage and exits 0, without inspecting a signal.

Keep this walkthrough synthetic. The summary prints contract identifiers, coverage and counts, without echoing raw input, label names, detector revisions or timestamps. Local validation does not establish a connected result plane, trained customer task, deployment, detection quality or rights to process customer data.

Inspect the exact source

Run these read-only commands in the authorized UMBRIQ checkout containing the pinned revision.

  • Command usage and limitsgit show a418fe85c8266966937f72c670d66e1fa4a10744:cmd/umbriq-signal/README.md
  • Inspector implementationgit show a418fe85c8266966937f72c670d66e1fa4a10744:cmd/umbriq-signal/main.go
  • Synthetic positive inputgit show a418fe85c8266966937f72c670d66e1fa4a10744:contracts/fixtures/contextual-signal/positive-complete-with-labels.json
  • Synthetic refusal inputgit show a418fe85c8266966937f72c670d66e1fa4a10744:contracts/fixtures/contextual-signal/negative-signal-carries-a-tenant.json
Back to UMBRIQ prerequisites