Fundamentals of Trust Engineering
Where Trust Thermodynamics meets the real world of felt human trust, stakeholder value safety, and human thriving at all scales.
By Sabino Marquez
Co-Founder & Chief Systems Strategist, Trustable.tv | TrustClub.tv
8CM: The Terminal Object in Trust Thermodynamics
8CM represents both the terminal object in the Trust Thermodynamics Model and the central value engineering specification for Trust Value organizations. It is where abstract trust theory becomes executable strategy, converting felt human trust into measurable, actionable primitives that guide every dimension of organizational value creation.
Strategic Impact Across the Value Journey
The 8 Trust Constituents and their Anti-Trust mirrors provide the affective acceptance surface that all trust artifacts and trust stories must activate. 8CM directly impacts:
- Customer Sub-Journey: 8CM defines what "safe" means for service continuity, incident handling, and disclosure posture, ensuring stakeholders can trust value delivery without fear of degradation or disruption
- Revenue Sub-Journey: Trust Stories compiled against 8CM target vectors accelerate gate clearance in diligence, procurement, and security review by activating the right constituents for exposed decision-makers
- Product Sub-Journey: Requirements are derived from Trust Personas, with each Trust Constituent translating into specifications for operational boundaries, evidence generation cadence, and proof of responsibility
- Valuation Sub-Journey: Evidence yield and constituent coverage become measurable inputs to capital allocation decisions, making trust production governable and forecastable at board and investor gates
This strategic positioning translates into specific operational capabilities that make trust production scalable and governable.
Why This Depth Matters
Organizations that treat trust as soft fail at gates where value is repriced, delayed, or denied. 8CM provides the specification layer that prevents this failure.
Operational Capabilities
Each constituent is decomposed into five measurable primitives with failure signatures, artifact surfaces, and behavioral indicators. This granularity enables:
- Sufficiency-grade evidence production at scale
- Trust Quality certification that prevents inert documentation
- Revocation surfaces when claims drift or break
- Affective Supply Chain compliance across tooling, artifacts, and stories
The Human Reality
The depth of 8CM (80 primitives across 16 constituents) exists because trust decisions are made by humans under exposure, not by frameworks under audit.
When a trust buyer must settle into "I can sign this" under scrutiny, they are evaluating Stakeholder Value Safety across all eight dimensions simultaneously.
8CM makes that evaluation legible, measurable, and engineered into every artifact the organization ships into the field.
8CM at a Glance
Each Trust Constituent represents a distinct dimension of felt trust, with its corresponding Anti-Trust Constituent representing the generated condition of trust collapse.
Clarity vs Confusion
Intelligibility, transparency, predictability, boundary explicitness, and semantic stability
Compassion vs Callousness
Attunement, benevolent intent, care in execution, patience, and repair orientation
Character vs Corruption
Moral restraint, truth commitment, duty integrity, fairness, and anti-hypocrisy
Competency vs Negligence
Reliability under load, correct execution, expertise alignment, and error discipline
Commitment vs Abandonment
Sustained dedication, follow-through, purpose integrity, and resilience in the face of challenges, defining true resolve.
Consistency vs Fluctuation
Predictable behavior, adherence to standards, and reliable performance, ensuring stability and uniformity over time.
Connection vs Isolation
Mutual understanding, shared purpose, active listening, and relational bridging, fostering genuine rapport and belonging.
Contribution vs Extraction
Generative engagement, value-adding action, shared growth, and active participation in collective well-being.
How Anti-Trust Constituents Are Generated
Anti-Trust Constituents are generated conditions produced when systems operate under the Compliance Dynamo, where coercion, extraction, and impunity dominate value exchange.
Compliance Dynamo Outputs
- Coercion: Force replaces consent
- Extraction: Value flows one-way
- Impunity: Accountability is structurally avoided
Medium Effects
- Medium conductivity drops (truth becomes expensive to transmit)
- Parasitic friction rises (rework, escalation, defensive behavior)
- Enclosure pressure rises (people route around formal channels)
Anti-Trust Constituents Generated
Anti-Trust Constituents emerge as measurable, predictable conditions.
Each Anti-Trust Constituent emerges when the system prioritizes throughput and narrative stability over stakeholder value safety. The Compliance Dynamo converts trust-building friction into trust-destroying conditions, making the anti-states measurable, predictable, and reversible through dynamo switching.
Deep Dive: The 8 Trust Constituents
For each constituent (Clarity, Compassion, Character, Competency, Commitment, Consistency, Connection, and Contribution), we will follow a consistent three-part structure:
The Constituent
Core concept
5 Primitives
Measurable components
Anti-Constituent
The collapse state
This systematic breakdown provides the primitive specification layer needed to effectively engineer trust into any system.
Clarity: Building Accurate Mental Models
Clarity is the felt condition where a person can form an accurate mental model of the system they are inside. The model covers obligations, interfaces, decision rights, enforcement, and recourse. The person expects stable interpretation across time and across actors.
Clarity reflects constraint, density, and friction as experienced through language, artifacts, and enforcement. It is evaluated at specific surfaces: policy surfaces, product behavior surfaces, support surfaces, enforcement surfaces, incident surfaces, and contractual surfaces.
The Five Primitives of Clarity
Intelligibility
The person can explain the system in plain language with low loss. Failure: Explanations require insider lore and comprehension varies by proximity to power.
Transparency
The system exposes relevant facts, constraints, and decision criteria at the point of need. Failure: Hidden criteria, selective disclosure, delayed disclosure after harm.
Predictability
Same inputs produce same outputs within expected variance. Failure: Outcome variance exceeds stated variance, exceptions dominate the rule.
Boundary Explicitness
Roles, ownership, decision rights, and escalation paths are explicit and discoverable. Failure: Responsibility ping pong, unresolved ownership, stalled escalation.
Semantic Stability
Terms retain meaning across documents, teams, and time. Failure: Term drift, contradictory definitions, definition by enforcement.
Confusion: The Anti-State of Clarity
Confusion is the felt condition where the person cannot build a reliable model of the system. Interpretation becomes costly. Compliance and silence become the safe strategy. Confusion is produced by opacity + volatility + interpretive punishment.
Confusion is compatible with high documentation volume and can be engineered with excessive artifact noise.
Opacity
Decision criteria inaccessible at point of need. People discover rules only during enforcement.
Volatility
Rules and enforcement shift without stable triggers or notice. Policy churn and sudden exception revocations.
Semantic Drift
Terms change meaning without explicit versioning. Competing glossaries and endless definitional disputes.
Hidden Selection
Outcomes depend on unstated attributes like status or proximity. Identical cases get different outcomes.
Interpretive Punishment
Attempting to interpret, ask, or clarify increases risk. People stop asking and route around formal channels.
Compassion: Treating Vulnerability as Real
Compassion is the felt condition where a person expects the system to treat their vulnerability as real, their friction as meaningful, and their harm as actionable. Compassion is expressed through burden bearing, care in execution, and repair behavior.
Compassion is legible under constraint. It is a medium property expressed at the human layer, reflecting how the system metabolizes friction without converting it into coercion, extraction, or impunity.
Compassion is evaluated at harm surfaces: support, incident response, enforcement, billing, escalation, and remediation.
The Five Primitives of Compassion
Attunement
The system notices the human state and adjusts interaction to reduce unnecessary harm. Failure: Scripted interaction that ignores context, distress, or constraint.
Benevolent Intent Attribution
The system defaults to good faith unless evidence requires otherwise. Failure: Suspicion as baseline, adversarial interpretation as default.
Care in Execution
The system handles people, data, and consequences with deliberate gentleness under load. Failure: Rough handling, dismissive tone, rushed closure, collateral damage treated as acceptable.
Patience Under Friction
The system tolerates clarification, iteration, and learning without status penalty. Failure: Friction triggers irritation, escalation, or punitive time pressure.
Repair Orientation
The system prioritizes restoration of dignity, capability, and safety after harm. Failure: Repair is avoided, delayed, outsourced to the harmed party, or treated as reputation management.
Callousness: The Anti-State of Compassion
Callousness is the felt condition where the system treats vulnerability as noise, friction as insubordination, and harm as an externality. Callousness has two modes: Neglect and Cruelty. Neglect is default in extraction systems. Cruelty appears when coercion is used to stabilize narrative and protect impunity.
Instrumentalization
Person treated as means to throughput, not stakeholder with standing. Interaction optimizes closure, deflection, or compliance.
Suspicion Baseline
System presumes bad faith and demands proof of legitimacy for basic care. Burden of proof imposed even for obvious harm.
Harm Minimization
System reframes harm as minor, normal, deserved, or not owned. Dismissal, gaslighting, blame inversion, forced self-justification.
Punitive Enforcement
Enforcement designed to increase pain to shape behavior. Threat, humiliation, reputational leverage, collective punishment.
Repair Denial
System treats repair as optional or as concession that weakens power. No apology, no restitution path, no learning loop.
Character: Integrity Under Incentive
Character is the felt condition where a person expects the system to remain bound to its stated constraints under incentive, pressure, and opportunity. Character is expressed as truthful dealing, fair application of rules, restraint with power, and acceptance of accountability.
Character reflects whether the system metabolizes friction through cooperative constraint or routes around constraint to preserve status, velocity, or impunity.
Character is evaluated at integrity surfaces: disclosure, enforcement, exceptions, incident handling, contracting, audit response, and executive commitments.
The Five Primitives of Character
Truthfulness
The system states what is true in relevant ways and does not rely on misdirection. Failure: Strategic ambiguity, selective truth, misleading omission, retrospective revision.
Fairness
Comparable cases are treated comparably, with deviations explicitly justified. Failure: Status dependent outcomes, favoritism, scapegoating, rule bending for the powerful.
Integrity Under Incentive
Incentives do not override stated constraints, especially under revenue, reputational, or schedule pressure. Failure: Constraint bypass during high stakes moments, quiet exception granting.
Restraint With Power
The system limits its own leverage and avoids unnecessary domination even when it can impose it. Failure: Threat leverage, punitive extraction, coercive bargaining, humiliation dynamics.
Accountability Acceptance
The system accepts responsibility, preserves traceability, and submits to consequence. Failure: Blame shifting, loss of traceability, punishment of truth tellers, refusal to own outcomes.
Corruption: The Anti-Trust Constituent of Character
Corruption is the felt condition where the system treats constraints as negotiable, truth as instrumental, and accountability as a threat. Corruption is incentive-aligned distortion of truth, rules, and consequence to protect power and preserve throughput.
Deception by Design
Communication and artifacts shaped to mislead while preserving plausible deniability. Over-disclosure that hides the relevant fact, wording engineered to misinterpret safely.
Selective Enforcement
Rules applied based on status, affiliation, or narrative utility. Exceptions for insiders, harsh enforcement for outsiders, inconsistent sanctions without justification.
Incentive Capture
Decisions and actions serve local incentives at the expense of stated constraints. Revenue over safety, speed over integrity, optics over correction.
Power Misuse
Authority used to extract, coerce, or silence rather than to steward. Threat based governance, retaliation, compelled agreement, suppression of alternatives.
Accountability Evasion
Traceability and consequence structurally avoided. Missing records, non-decision decisions, scapegoats, engineered ambiguity, refusal to submit to review.
Competency: Execution Quality Under Load
Competency is the felt condition where a person expects the system to execute its stated functions safely, correctly, and reliably under normal conditions and under stress. Competency is expressed as sound judgment, controlled failure modes, preparedness, and consistent delivery of intended outcomes.
Competency is legible when conditions degrade. It reflects whether the system can metabolize complexity without converting it into harm, volatility, or cascading error.
Competency is evaluated at execution surfaces: product behavior, operational response, change management, incident handling, reliability engineering, and customer facing support accuracy.
The Five Primitives of Competency
Skill Sufficiency
The system has the knowledge and capability to perform the work it claims to perform. Failure: Repeated basic errors, reliance on heroics, chronic dependency on a few individuals.
Judgment Quality
Decisions are made with appropriate inputs, tradeoffs are explicit, and second order effects are considered. Failure: Impulsive decisions, unexamined tradeoffs, repeated predictable surprises.
Reliability Under Load
Performance degrades gracefully under stress within an expected variance band. Failure: Cascading failures, chaotic degradation, frequent customer visible instability.
Preparedness
Anticipated scenarios have plans, instrumentation, and rehearsed responses. Failure: Surprise is the default, playbooks are missing or unused, response is improvised.
Error Containment
Failures are bounded in scope and time, with fast detection and safe rollback paths. Failure: Silent failures, long detection windows, blast radius growth, unsafe rollouts.
Negligence: The Anti-State of Competency
Negligence is the felt condition where the system operates beyond its capability, treats predictable failure as acceptable, and externalizes the costs of error onto stakeholders. Negligence is not a single mistake but a pattern of unprepared execution that normalizes harm and hides incapacity behind throughput.
Capability Misrepresentation
Claims exceed actual ability, coverage, or readiness. Marketing or leadership claims outpace operational reality; repeated gap revelations.
Decision Shallowness
Decisions ignore relevant inputs, omit tradeoffs, and exclude those who bear the consequences. Rework cycles, repeat incidents from known causes, preventable regressions.
Fragility Under Stress
Small perturbations cause outsized failure and unpredictable behavior. Frequent escalations, unstable dependencies, brittle architectures.
Unpreparedness
Known scenarios lack plans, telemetry, or rehearsals. Incident response is ad hoc; knowledge is tribal; drills are absent.
Failure Sprawl
Failures propagate because boundaries, controls, and rollback paths are missing or unused. Large blast radius, long recovery, repeated "we could not reproduce" postures.
Commitment: Carrying Obligations Through Time
Commitment is the felt condition where a person expects the system to carry obligations through time. Commitment is expressed as durable prioritization, follow through, cost bearing when commitments become expensive, and presence during incidents.
Commitment is legible as temporal integrity. It reflects whether the system preserves continuity of intent under incentive shifts, shocks, and convenience pressures.
Commitment is evaluated at temporal surfaces: roadmap promises, contractual obligations, service ownership, long tail support, remediation promises, and incident follow through.
The Five Primitives of Commitment
Priority Allocation
Commitments receive real resources, attention, and executive backing over time. Failure: Chronic under-resourcing, "important" commitments repeatedly deferred.
Follow Through
Promises convert into delivered actions with clear completion criteria. Failure: Endless "in progress," partial delivery framed as completion, repeated resets.
Durability Under Pressure
Commitments hold when incentives shift, budgets tighten, or deadlines compress. Failure: Commitments abandoned during revenue moments, cost cutting, or leadership changes.
Cost Bearing
The system absorbs the costs of keeping its commitments rather than externalizing them. Failure: Stakeholders bear remediation costs, switching costs, or operational burden from broken promises.
Presence During Incidents
The system stays engaged, communicates, and acts until the obligation is actually resolved. Failure: Disappearing after initial response, delegating to scripts, premature closure.
Abandonment: The Anti-State of Commitment
Abandonment is the felt condition where commitments decay, vanish, or become conditional when they become inconvenient. Abandonment is not a single missed deadline. Abandonment is a pattern of temporal unreliability where obligation performance is subordinated to convenience, optics, or short term incentive.
Rhetorical Commitment
Commitments exist primarily as language, not as resourced obligation. High promise volume with low delivery, vague timelines, shifting definitions of done.
Deferral Normalization
Delays are routine and unaccounted, treated as acceptable drift. Reprioritization without acknowledgment, chronic backlog burial.
Incentive Switching
Commitments change with leadership, quarterly targets, or narrative need. Support withdrawn after purchase, roadmap reversals without restitution.
Cost Externalization
The costs of broken commitments are pushed to the stakeholder. Forced workarounds, paid upgrades for promised capability, unreimbursed harm.
Disengagement
The system withdraws attention before resolution and avoids ownership. Silent handoffs, stalled communication, closure without satisfaction.
Consistency: Stable Patterns Across Time and People
Consistency is the felt condition where a person expects the system to behave the same way across time, across people, and across comparable cases. Consistency is expressed as stable rules, stable enforcement, stable operating rhythms, and stable interpretation boundaries.
Consistency is legible as low variance in treatment. It reflects whether the system maintains a coherent operating pattern rather than allowing power, mood, or narrative need to drive variance.
Consistency is evaluated at variance surfaces: policy interpretation, enforcement outcomes, service delivery, incident response, exception granting, and decision cadence.
The Five Primitives of Consistency
Rule Stability
Rules and expectations remain stable across time and are changed through explicit governance. Failure: Policy churn, silent rule changes, retroactive rules.
Enforcement Symmetry
Comparable cases receive comparable enforcement, with deviations explicitly justified. Failure: Status-based outcomes, selective enforcement, arbitrary sanctions.
Procedural Regularity
Core processes run with dependable cadence, inputs, and outputs. Failure: Ad hoc processes, changing steps, missing checkpoints.
Interpretation Stability
Terms, thresholds, and decision criteria are interpreted consistently across actors. Failure: Interpretive variance across managers, contradictory guidance, "depends who you ask."
Change Governability
When change occurs, it is versioned, communicated, and bounded with clear transition rules. Failure: Unannounced changes, undefined transition periods, surprise breaking changes.
Inconsistency: The Anti-State of Consistency
Inconsistency is the felt condition where rules, enforcement, and processes shift without stable triggers, without versioning, and without recourse. Inconsistency makes compliance the rational survival strategy because prediction is expensive and variance is dangerous. Inconsistency is compatible with high documentation volume and can be engineered through churn, exception culture, and interpretive ambiguity.
Policy Churn
Rules and expectations change frequently or unpredictably. Failure: Stakeholders cannot track current rules; frequent retraining is required.
Arbitrary Enforcement
Enforcement shifts based on mood, pressure, status, or narrative utility. Failure: Sudden crackdowns, uneven sanctions, exceptions without record.
Process Drift
Processes change without explicit redesign or documentation. Failure: People execute different versions of the same process simultaneously.
Interpretive Divergence
Different actors apply different meanings and thresholds to the same terms. Failure: Conflicting decisions on identical cases; endless escalation loops.
Ungoverned Change
Changes are unversioned, uncommunicated, and lack transition protections. Failure: Breaking changes appear without notice; recourse is absent.
Connection: Social Standing and Belonging
Connection is the felt condition where an individual experiences the system as socially and structurally inclusive of them. It covers aspects like recognition, belonging, safety, reciprocity, and active participation in shared sensemaking. Connection is evaluated by whether a person feels they have standing, with an expectation to be treated as a valued stakeholder possessing a voice and dignity within the system.
The Five Primitives of Connection
Recognition
The system acknowledges the person as a legitimate participant with context and history. Failure: Treated as anonymous, interchangeable, or reset to zero each interaction.
Belonging Safety
The person can participate without fear of humiliation, demotion, or social punishment. Failure: Status threats, ridicule, retaliation, silent exclusion.
Respect
Interaction maintains dignity and avoids objectification or contempt. Failure: Dismissive tone, demeaning process, forced self-justification rituals.
Reciprocity
The system demonstrates mutual obligation and two-way exchange rather than one-way extraction. Failure: One-way demands, asymmetric burden, requests treated as nuisance.
Shared Sensemaking Access
The person can access and contribute to the meaning-making process around decisions and events. Failure: Decisions happen elsewhere. Explanations are post hoc. Input is performative.
Alienation: The Anti-State of Connection
Alienation is the felt condition where the person experiences social severance, reduced standing, and exclusion from meaning-making. Alienation fragments the medium. It converts people into isolated units who comply to avoid harm. Alienation is compatible with high communication volume and can be engineered through performative inclusion, status gating, and ritualized processes that deny voice.
Anonymization
The person is treated as an interchangeable case rather than a situated participant. Failure: Repeated re-introduction, no memory of history, no continuity across interactions.
Status Gating
Access to attention, recourse, and influence depends on rank or proximity. Failure: Only insiders get resolution. Others get scripts and delay.
Social Threat
Participation increases risk of humiliation, demotion, or retaliation. Failure: People self-silence. Dissent disappears. Questions stop.
Contempt Signaling
The system communicates low regard for the person or their needs. Failure: Dismissal, sarcasm, blame framing, moralizing.
Exclusion from Sensemaking
The person cannot influence interpretation of events that affect them. Failure: Post hoc explanations. Decisions made in closed loops. Input ignored without acknowledgment.
Contribution: Meaningful Usefulness and Mutual Benefit
Contribution is the felt condition where a person experiences their participation as meaningfully useful to the system and mutually beneficial in outcome. Contribution is expressed as impact visibility, fair credit, stewardship of effort, and reciprocal value flow.
Contribution is legible as non-wasted life force. The person expects their work, attention, data, or sacrifice to produce shared benefit rather than being extracted and discarded.
Contribution is evaluated at value exchange surfaces: labor, attention, data provision, compliance burden, feedback loops, and remediation effort.
The Five Primitives of Contribution
Usefulness
The person's input is applied in ways that matter to outcomes and system improvement. Failure: Input disappears into a void. Feedback is performative. No observable effect.
Impact Visibility
The system makes the effects of contribution legible, traceable, and attributable. Failure: No line of sight from effort to outcome. Credit is opaque.
Credit Fairness
Recognition and reward track actual contribution rather than status or proximity. Failure: Credit capture by elites. Invisible labor. Misattribution.
Stewardship of Effort
The system minimizes wasted work, unnecessary burden, and redundant process. Failure: Busywork, rework, ritual compliance, repetitive requests for the same data.
Mutual Benefit Expectation
The exchange is reciprocal. The system bears obligations and returns value in proportion to what it takes. Failure: One-way extraction. Stakeholder bears costs. Value flows upward only.
Exploitation: The Anti-State of Contribution
Exploitation is the felt condition where the system treats stakeholder input as extractable fuel rather than as valued participation. Effort is taken without reciprocal benefit. The system captures surplus while externalizing cost. Exploitation is often stabilized by narrative that reframes extraction as opportunity or duty. Exploitation is compatible with high praise volume and can be engineered through opacity of outcomes, status-based credit capture, and coercive burden shifting.
Appropriation
The system takes effort, data, or sacrifice without reciprocal return. Failure: Increasing demands with declining benefit. No restitution.
Impact Obscuration
Outcomes are hidden or untraceable, preventing accountability for conversion of input. Failure: No metrics. No attribution. Credit fog.
Credit Capture
Rewards and recognition detach from actual contribution and follow status. Failure: Managers and elites receive credit for others' labor.
Burden Shifting
Costs and friction are pushed down onto those with least power. Failure: Unpaid overtime, forced workarounds, self-service as default, endless documentation demands.
Disposability
The system treats contributors as replaceable and does not invest in their continuity or wellbeing. Failure: High churn accepted. Burnout normalized. Loss treated as irrelevant.
Introduction to the TVM 8CM Object