Lineage and Launch.

§Ithe ancient lineage

The mechanics are old; the rupture is new

Across rhetoric, oratory, ritual, ceremony, memory arts, crowd psychology, propaganda, education, spiritual formation, and public spectacle, the same eight-step mechanism keeps appearing: get attention, attach emotion, make it memorable, give it a frame, repeat it socially, tie it to identity, ask for action, make repair difficult. That is not a modern discovery. It is what every persuasion tradition has been working with for two and a half millennia.

The modern cognitive-domain frame is new. The mechanics it describes are not.

The Aristotelian to Digital Gravity translation

Cicero's five canons as operator workflow

Invention (select payload), arrangement (sequence the effect chain), style (shape the emotional surface), memory (make it retainable), delivery (choose voice, channel, timing). This is operator language fifteen hundred years before there were operators.

The deep eight-step pattern

capture → tag → encode → frame → repeat → identity-tie → action → repair-difficulty

The same pattern shows up in classical rhetoric, monastic formation, ritual ceremony, advertising, broadcast propaganda, and feed-native cognitive operations. What changed is not the pattern; it is the cost of running it.

What old thinking missed

The old systems understood persuasion. They did not have real-time telemetry at population scale, algorithmic optimization loops, generative payload production, synthetic personas, personalized targeting, automated A/B testing of emotion, cheap deepfakes, or feed-level behavioral measurement. Aristotle had pathos. The feed has pathos plus telemetry. That is the rupture.

The defensive lineage is also old

Stoic discipline taught noticing the impression before assenting to it. Socratic questioning slowed the claim down. Monastic discernment treated thoughts that appear in the mind as not necessarily yours and not necessarily to be obeyed. Civic rhetoric taught citizens how persuasion works so they would not be ruled by it unconsciously. Ritual repair built confession, restitution, council, witness, and reintegration because correction alone is not repair. That last tradition is the one Digital Gravity most directly inherits.

The inversion

Old persuasion asks: how do I move the audience? Digital Gravity asks: how do I teach the audience to notice being moved?

Old rhetoric asks: how do I make this memorable? Digital Gravity asks: what memory path did this wear, and what residue remains after correction?

Old propaganda asks: how do I make the signal travel? Digital Gravity asks: what repair system can metabolize the damage after it travels?

§IIthe public exposure event

The expected sequence (3–6 months out)

If the work catches, expect this progression: language travels first → people simplify it → adjacent communities claim it → critics test the weak points → vendors try to operationalize it → bad actors strip the ethics from it → you are forced to clarify the canon. This is normal when a framework starts to move. The point is to prepare before it moves.

What can be anticipated

Simple phrases travel first. "Trust is infrastructure." "Verification is not trust." "Correction is not repair." "The payload changes; the pipeline does not." These will detach from the discipline. The anti-paranoia clause must travel with them.

People will collapse trust into "risk score." This is the first major conceptual failure. The canonical reply: KTP computes earned autonomy for operational systems. It does not exhaust relational trust. A trust score is not trust; it is a governance signal inside a trust infrastructure.

Cognitive-domain framing will attract two audiences. One thoughtful, one tactical. The dual-use problem is real. The non-negotiable boundary: Propaganda uses the pipeline and hides it. Digital Gravity uses the pipeline to reveal the pipeline. This is a control, not a sentence. The dual-use cut is implemented at /research/cognitive.

Scholars will attack overclaiming first. Not "this is uninteresting" — they will say physics language is metaphorical, percolation is overextended, simulations are toy models, variables are unvalidated. Some of those critiques will be fair. Visible humility is the protection.

Operators will treat it as influence literacy. Partly right, incomplete. Digital Gravity is not reducible to media literacy, disinformation, zero trust, AI governance, or platform safety. A canonical taxonomy prevents flattening.

Enterprises will ask for a tool before the theory is ready. The correct first product is a diagnostic worksheet, not a score. Your Trust Infrastructure Score is 78 is the wrong artifact. The Trust Infrastructure Audit is the right one.

You may become the bottleneck. People will want you to explain everything. The Canonical Stack is the answer to this — say the same thing the same way every time.

The Canonical Stack

Read alongside the Trust Force Equation, the Kinetic Trust Protocol is not a parallel project but the substrate the equation requires to have a domain. The equation describes the physics of accumulated trust: costly signal, co-presence, reciprocity, integrated over time. KTP supplies what the equation cannot supply for itself: vector identity (the precondition that the integral has a stable pair of parties across time), substrate ceiling (the structural cap set by what the substrate can carry), and cryptographic cost (the floor that prevents witnessed cost from collapsing to zero). The two layers compose. Without the physics, the substrate is unmotivated infrastructure. Without the substrate, the physics has no domain.

The pieces are connected. They are not interchangeable. See the full stack.

The three non-negotiable controls

The ethical boundary. If the essay opens vulnerability, it must return an instrument. If it names a pipeline, it must teach the reader to see the pipeline. If it shows harm, it must ask who owns repair. If it uses cognitive force, it must disclose the force. Reader must leave with more agency than they entered. /canon/ethics.

The claims register. A visible table that distinguishes public thesis (trust is infrastructure), theory claim (trust builds slowly, betrayal damages discontinuously), research hypothesis (Ostrom-percolation), candidate hypothesis (DP9 temporal edge persistence), operational protocol (KTP), and writing method (DCTI). Each row gets evidence, risk, and what would weaken it. /canon/claims.

The anti-paranoia clause. Not every signal is an operation. Not every viral thing is hostile. Most culture is organic. Paranoia is itself a form of capture. The discipline is discernment, not suspicion. This is recurring house doctrine, not a one-time disclaimer.

The blind spots

The framework can become the thing it critiques. Readers can collapse into paranoia. The "operator" frame can militarize the public imagination. KTP can be mistaken for surveillance infrastructure. Public novelty can outrun scholarly validation. The public may want remedies faster than they can be responsibly provided. The framework may be too beautiful to test honestly. Institutional resistance will arrive disguised as compliance. The emotional labor will be heavy and personal exposure real. Bad-faith reframing — "this is just vibes with math," "this is social credit," "this is censorship," "this is paranoia," "this is not new" — must be answered before critics own the frame.

§IIIthe second-order build

The principle

The second-order work is not more content. It is containment. Build the container before the signal scales.

Containment artifacts

The Stack page. The Claims Register. The Glossary. The "What This Is Not" page. The Ethics / Safety Note. The Falsification page ("how this could be wrong"). The Evidence Notes / source room. The Editorial Method Manual. The Threat Model. The Trusted Review Circle. The Reader Pathways page. The Trust Infrastructure Audit v0.1 (worksheet, not score). The Signal Propagation Diagnostic v0.1 (defensive counterpart to ACPP). KTP in Plain English with the red lines.

Wave 1 of the canon ships stack, claims, limits, glossary, ethics. Repair, responsible-use, doctrine, evidence, audit, plain-english KTP follow.

Reader pathways

Trust Infrastructure Audit v0.1

Nine tests: trust object, load-bearing, cost, witness, reciprocity, repair, horizon, residue, owner. A worksheet, not a score. The first product is a diagnostic, not a dashboard.

Signal Propagation Diagnostic v0.1

Seven questions: what caught attention, what emotion did it tag, what first version did it plant, what evidence arrived pre-weighted, what action did it compress, what residue remained after correction, who owned repair.

KTP red lines

No permanent person score. No hidden human scoring. No unappealable autonomy denial. No indefinite memory without expiration. No purpose drift. No surveillance without attestation. No trust computation without repair path. No use beyond declared domain. /canon/limits.

Publication sequence

Pattern: diagnosis → instrument → diagnosis → repair → operationalization. The Trust Integral (what trust is) → Six Seven (how signals move faster than repair) → The Repair Rate (what repair infrastructure requires) → The Trust Contract (what must be true before a signal crosses a boundary) → The Mayordomo for the Feed (acequia governance translated to digital stewardship) → KTP in Plain English (operational bridge). Don't leave readers in dread for too long.

§IVpersonal and strategic

Operating rhythm

Weekly: one writing block, one evidence/source block, one review/critique block, one embodied reset, one no-output thinking block. Do embodied work after cognitive-domain writing. Don't publish from a fresh wound.

Personal boundaries

Don't argue with every critic. Don't become tech support for everyone's awakening. Don't let public pace set theory pace. Don't collapse personal identity into the framework. You can build the ditch. You cannot carry everyone's water.

Strategic hierarchy

Not movement, research program, and implementation protocol all equally. The hierarchy: public framework (Digital Gravity / Trust is Infrastructure) → research frame (Relational Trust Infrastructure) → operational frame (KTP) → application frame (Tamed Autonomy). A public framework anchored by a research program, with KTP as one implementation pathway. Hold that hierarchy when people try to flatten it.

§Vthe unified principle

The two documents say the same thing from opposite ends.

The first looks backward and finds that the mechanics Digital Gravity describes have been understood in fragmentary form for two and a half millennia — by rhetoricians, ritualists, mnemonists, propagandists, and advertisers. The framework's contribution is not that it discovered the mechanics. It's that it makes them visible at scale, in the specific historical moment when they have been industrialized by telemetry and AI.

The second looks forward and recognizes that making the mechanics visible uses the same channels the mechanics travel through. Reveal-the-pipeline writing is itself a movement through the pipeline. The ethical difference is disclosure. The operational consequence is that the framework will scale through the same dynamics it diagnoses, and will therefore need its own trust infrastructure: claims register, glossary, ethics boundary, anti-paranoia clause, falsification page, review circle, repair-oriented sequencing.

That is the through-line.

end of report.