Implementation companion · HCQ Record

Making the development of quality understanding visible.

VerityJX now presents Test Analyst, Test Manager and Test Architect as working professional expressions. This companion shows how their different perspectives can meet in one practical, technology-neutral HCQ Record.

Start with the Practice.

This page does not redefine Human-Centred Quality. Start with the Professional Expressions comparator v0.1. The expressions are deliberately non-authoritative working propositions; use this implementation companion to consider how attributed contributions from different professional lenses can remain visible in one durable record.

One record, multiple professional expressions.

A Test Analyst may contribute an observation close to behaviour; a Test Architect may recognise a systemic relationship; a Test Manager may help connect perspectives to consequential judgement. These are vantage points, not role assignments. The record belongs to the developing understanding.

One developing record

From observation to stewarded learning

The record may begin incomplete. Each contribution remains distinguishable from what came before.

Observe

Three test executions timed out after submission during peak-load testing.

Preserve: source evidence, context, contributor and time.

Interpret

Possible capacity degradation; alternatively, delayed confirmation may cause users to resubmit.

Preserve: multiple interpretations and material uncertainty without overwriting the observation.

Understand

The transaction may succeed while confirmation is delayed; the quality concern includes the user's ability to know what happened.

Preserve: the best current coherent explanation and what remains unknown.

Judge

Treat this as release-relevant uncertainty, not merely an isolated performance defect.

Preserve: rationale, consequence and contributors.

Improve

Validate duplicate-submission safeguards and explicit submission-state feedback.

Preserve: intended outcome and return later for actual outcome.

Steward

Delayed acknowledgement can convert a performance symptom into a user-decision and duplication risk.

Preserve: reusable learning with provenance, not detached folklore.

The record is not the tool.

The same information model could be represented in XML/JSON, a relational or lakehouse store, a test-management extension, a document, or another structured platform. The implementation is allowed to change. The distinctions between evidence, interpretation, understanding, judgement, outcome and stewardship should not disappear because a technology makes them inconvenient.

A practical implementation question

What could your existing tools already provide?

Contribution does not require inventing another platform. A practitioner may discover that execution evidence already lives in one system, telemetry in another and decisions elsewhere. The HCQ challenge is to preserve the development of understanding across them without duplicating everything.

Contribute what practice reveals