Behavioral
Behavioral

Perimeter Technology Ethics

Behavioral Mechanics

Perimeter Technology Ethics

Most technology ethics asks whether a tool is good or bad in the abstract — privacy, bias, harm at scale.
developing·concept·1 source··Jun 2, 2026

Perimeter Technology Ethics

Five Questions to Ask a Tool Before You Let It In

Most technology ethics asks whether a tool is good or bad in the abstract — privacy, bias, harm at scale. The user's Solar Idealism framework — the user's own developing synthesis of Donovan, Billinge, and Bell, not a technology-ethics literature1 — asks a sharper, more personal question: does this tool strengthen me or weaken me? It proposes a five-question test for any technology, run at the perimeter — the boundary of your life, your attention, your sovereignty — before you let the tool across. The framework's verbatim sketch is the five-question solar tech test1: a checkpoint at the gate, deciding what gets in.

The framework's move is to treat technology like anything else crossing the perimeter (Perimeter as Sacred Boundary): not neutral, not automatically welcome, but interrogated for whether it serves the solar direction (ascent, sovereignty, capability, order) or the anti-solar one (dissolution, dependency, comfort, fragmentation). That's a genuinely useful reframe — it converts the vague unease many people feel about their devices into five concrete questions — and it carries a real risk of techno-pessimism, of a reactionary "all new tools weaken us" Luddism, and of a "strengthen vs. weaken" test so subjective it just ratifies the user's prejudices. This page works the test as the framework's applied technology-ethics, and marks where it curdles into reflexive anti-modernism. The source flags this section as suggestive1; the page develops the sketch and reconstructs the five questions from the framework's perimeter-and-sovereignty logic.

What This Actually Is

The model treats every technology as something crossing your perimeter and applies the framework's gatekeeping logic to it. Reconstructed from the framework's core architecture, the five-question solar tech test asks, of any tool, whether it serves the solar or the anti-solar direction:1

  1. Strength or weakness — does using this build my capability over time, or atrophy it? (The calculator that erodes mental math vs. the tool that extends real capacity.)
  2. Sovereignty or dependency — does this leave me more self-authoring, or more dependent on a system I don't control? (The skill I own vs. the platform that owns me.)
  3. Ascent or comfort — does this serve the upward aim, or does it sedate me into comfortable dissolution? (The tool that frees time for the work vs. the one that fills the time with pleasant nothing.)
  4. Order or fragmentation — does this integrate my attention and life, or shatter it? (The instrument that focuses vs. the feed that fragments.)
  5. Perimeter integrity or dissolution — does this respect the boundary of my sovereign space, or dissolve it? (The tool I command vs. the one that colonizes my attention and surveils my interior.)

The test belongs in behavioral-mechanics because it's a tactical decision-protocol — a concrete procedure for the choice of whether to admit a tool, applied to one's own life or prescribed to others. It's not a theory of technology; it's a gate-keeping practice. The page works the test's logic, then the techno-pessimism and subjectivity risks. (Its AI-specific application is developed at AI Ethics — Solar Framework, which runs the same five questions on AI tools specifically.)

The Internal Logic — The Tool Is Not Neutral, and Neither Is the Default

The framework's logic rejects the "technology is neutral, it's all in how you use it" cliché. Its claim: tools have gradients — they make some uses easy and others hard, and over time the easy uses shape the user. A feed engineered for engagement doesn't just allow fragmented attention; it trains it. A tool that does your thinking doesn't just offer convenience; it atrophies the capacity it replaces. So the question isn't "can this be used well?" (almost anything can, in principle) but "what does this tool's gradient pull me toward, by default, over years?" The perimeter-test exists because the default matters more than the possibility: you won't heroically resist a tool's gradient every day for a decade; you'll mostly slide down it. So you decide at the gate, before the gradient has you.

The five questions are the framework's solar/anti-solar polarity (the solar/lunar axis, the whole ascent-vs-dissolution architecture) applied to that gradient. Solar tools build strength, sovereignty, ascent, order, and respect the perimeter; anti-solar tools build weakness, dependency, comfort, fragmentation, and dissolve the perimeter. The test is a way of reading a tool's gradient against that polarity before admitting it — gatekeeping at the boundary rather than fighting the tool's pull after it's already inside.

But the logic has a reactionary failure mode built in, and the framework leans toward it. The solar/anti-solar polarity can be applied to brand all novelty as dissolution. "Comfort" is coded anti-solar, and almost any new tool offers some comfort, so a lazy application of the test condemns nearly everything new as weakening, dependency-creating, comfort-sedating — producing a reflexive anti-modernism where the wise solar man rejects the smartphone, the AI, the convenience, on principle. That's not discernment; it's nostalgia with a rubric. The genuine version of the test distinguishes tools whose gradient genuinely atrophies capacity and colonizes sovereignty (real) from tools that are merely new and comfortable (not automatically anti-solar) — and the framework's polarity, applied carelessly, collapses that distinction. The test's value (it makes the gradient-question concrete) and its danger (it can rubber-stamp Luddism) run through the same five questions, depending on whether they're applied with discernment or with prejudice.

Synergies & Handshakes — What the Test Gives the Vault

The test gives the corpus a concrete decision-protocol for the technology question, converting the diffuse modern unease about devices into five answerable questions run at a clear decision-point (the gate, before admission). It connects the framework's perimeter-cosmology to one of the most practical daily decisions a person makes — what tools to let into their attention and life — and it's genuinely more actionable than abstract tech-ethics, because it's run at the personal perimeter where the user actually has control.

Its second gift is the gradient-not-neutrality insight: the recognition that tools train their users via their defaults, so the decision that matters is at the gate (admit or not) rather than in the heroic daily resistance to a tool already inside. That's a real and useful correction to the "it's neutral, just use it well" complacency — most people lose the daily fight with a tool's gradient, so the leverage is at admission. This insight is portable to any habit-or-environment-design question, not just technology.

Analytical Case Study: The Smartphone at the Gate

Run the five questions on the smartphone — the technology most people never actually decided to admit, that simply arrived and colonized — and the test shows both its edge and its trap.

Strength or weakness? The phone extends real capability (navigation, communication, access to the world's information) — and atrophies others (memory, navigation-without-GPS, sustained attention, tolerance for boredom). Mixed, and the test demands you weigh which gradient dominates for you rather than accept the marketing's "it's all capability."

Sovereignty or dependency? Here the test bites hard: the phone leaves most users deeply dependent on systems they don't control (the platforms, the algorithms, the attention-economy that monetizes them) — sovereignty mostly lost, the device commanding the user more than the reverse.

Ascent or comfort? For most users, the honest answer is comfort/sedation — the phone is the single greatest source of pleasant dissolution ever engineered, the feed a perfectly-optimized anti-ascent machine.

Order or fragmentation? The phone is the paradigm fragmentation-device — designed to shatter attention into engagement-sized pieces. Clear anti-solar reading.

Perimeter integrity? The phone is the great perimeter-dissolver — it colonizes attention, surveils the interior, erases the boundary between sovereign space and the always-on demand. Strong anti-solar reading.

The test's verdict on the smartphone-as-used-by-default is damning, and largely correct — this is the test at its best, naming precisely why the device most people never chose is the one most corrosive to sovereignty and attention. But here's the trap the case study must show: the test's verdict is on the default relationship, and a disciplined user can change the relationship (a stripped phone, no feeds, command-not-colonization). The lazy application says "the test condemns the smartphone, reject it" — Luddism. The discerning application says "the test names the smartphone's gradient as strongly anti-solar, so admit it only with the specific disciplines that reverse the gradient, or not at all" — discernment. The difference between the two applications is the difference between the test as a tool of wisdom and the test as nostalgia with a rubric. The case study's payoff: the five questions give a genuinely sharp reading of why the smartphone corrodes — and whether that reading produces reactionary rejection or disciplined admission depends entirely on whether the test is run with discernment or with prejudice.

Implementation Workflow: Running the Test at the Gate

A new tool wants in — an app, a platform, an AI assistant, a device. The framework's discipline is to run the five questions at the gate, before the tool's gradient has a year to shape you, and to run them honestly rather than as a foregone conclusion. You sit with the tool not yet admitted and you ask, concretely, about your likely default relationship with it (not the heroic best case the marketing sells).

Strength or weakness: over a year of normal use, will this build a capability or atrophy one? You name the specific capacity at stake. Sovereignty or dependency: will this leave you more self-authoring or more dependent on a system you don't control — and who owns the thing you'd come to rely on? Ascent or comfort: will this free you toward the work, or sedate you into pleasant nothing? You're honest about which way the tool's gradient actually pulls, not which way you'd like to think you'd use it. Order or fragmentation: will this integrate your attention and life, or shatter them? Perimeter integrity: will you command this tool, or will it colonize your attention and surveil your interior?

Then the discerning judgment — the part that separates wisdom from Luddism. You don't tally a score and reject anything with "comfort" in it. You ask: is the anti-solar gradient inherent to the tool, or to my default use of it — and can I admit the tool with disciplines that reverse the gradient? A tool with a strong anti-solar default (the smartphone, the feed) can sometimes be admitted under specific constraints that flip its gradient (the stripped device, the deleted feeds, the command-relationship); a tool whose anti-solar pull is irreversible (the slot-machine app, the engagement-trap with no disciplined-use mode) gets refused at the gate. You write down, for any tool you admit with a strong anti-solar gradient, the specific disciplines that reverse it — because admitting it without them is just sliding down the gradient you correctly identified.

The final check is the prejudice-audit: am I rejecting this because the test genuinely reads it as capacity-atrophying and sovereignty-dissolving, or because it's new and I'm dressing nostalgia as discernment? The test is only wisdom if it can sometimes say yes to the new; if it always says no, it's Luddism wearing a rubric.

The Perimeter-Tech Failure: Luddism With a Rubric

The test fails into reactionary anti-modernism — the user who runs the five questions as a foregone conclusion, condemns all novelty as dissolution, and mistakes nostalgia for discernment. You recognize it by the always-no: every new tool fails the test, the wise solar man rejects the smartphone and the AI and the convenience on principle, and "this weakens us" is the verdict before the questions are honestly run. This isn't sovereignty; it's a different kind of capture — captured by the past, by the prejudice that new = weakening. A test that can't say yes to anything new isn't a discernment tool; it's a confirmation engine for technophobia.

The second failure is the subjectivity collapse — the test's questions ("strength or weakness," "ascent or comfort") have no objective measure, so they collapse into "tools I like pass, tools I distrust fail." The framework supplies the five questions but no calibration for answering them, so the test can ratify whatever the user already believed. The discipline against this is the honest default-reading (what will my real relationship with this be, not my idealized one) and the prejudice-audit — but the framework supplies the questions more clearly than the calibration, so the subjectivity-collapse is the test's most common quiet failure.

The framework's own failure is the polarity's anti-comfort bias. By coding "comfort" as anti-solar, the test is structurally tilted against nearly everything that makes life easier — which is most technology. A framework whose tech-ethics is built on a polarity that reads ease as dissolution will, applied honestly, tend toward reactionary rejection, because ease is exactly what tools provide. The vault documents the gradient-insight as genuinely valuable and the anti-comfort tilt as the structural bias that breeds Luddism, requiring the discernment-discipline the framework under-supplies.

Evidence / Tensions / Open Questions

Evidence. The test is the user's synthesis applying the perimeter-polarity to technology; the source stub flags it as suggestive.1 The gradient-not-neutrality insight has strong independent company — the "technology is not neutral" tradition (Postman, attention-economy critique, the documented engagement-optimization of feeds, the deliberate-design-for-dependency of attention-capture platforms). So the test's core insight is well-supported. Its anti-comfort tilt and Luddism-risk are the framework's own, not shared by the more discerning tech-critics it converges with (who distinguish corrosive design from mere novelty).

Tensions.

Techno-pessimism / reactionary Luddism. [TENS] The polarity's anti-comfort coding tilts the test toward rejecting all novelty as dissolution. The framework supplies the questions but not the discernment that distinguishes corrosive tools from merely new ones — so the test, applied carelessly, becomes nostalgia with a rubric. Document the gradient-insight as valuable and the always-no tendency as the failure to guard against.

The subjectivity problem. [TENS] "Strength or weakness," "ascent or comfort" have no objective measure; the test can ratify the user's prejudices. The framework under-supplies calibration, leaving the answers vulnerable to motivated reasoning in either direction.

The perimeter-logic's blind spots. The test is run at the personal perimeter (what I admit into my life), which is its strength (actionable, where the user has control) and its blind spot — it has little to say about technology's collective and structural effects (a tool can pass your personal perimeter-test and still be socially corrosive at scale). Personal gatekeeping isn't a complete tech-ethics.

The genuine value, honestly stated. The gradient-not-neutrality insight and the gate-not-daily-resistance leverage-point are real and useful, with respectable independent company. The danger is the anti-comfort tilt and the subjectivity, not the gatekeeping principle. The honest position keeps the test and adds the discernment-discipline.

Open questions (tracked in META):

  • What calibrates the five questions? Without a measure, the test ratifies prejudice. Is there a way to answer "strength or weakness" that isn't just the user's bias — e.g., a year-later capability check?
  • Can the test say yes to the genuinely new? A discernment tool must sometimes admit novelty. What distinguishes the framework's test from technophobia, in practice rather than in principle?

Author Tensions & Convergences

The test is the user's synthesis; the authors supply the disposition. Donovan supplies the perimeter-and-sovereignty logic that makes "gatekeep the tool at the boundary" natural, and a broader skepticism of soft modernity that tilts toward the anti-comfort bias. Billinge contributes the somatic-sovereignty instinct (the body and its capacities as the thing technology can either extend or atrophy). Bell supplies the ascent-vs-dissolution polarity that the five questions encode.

What the assembly reveals — and where the page is most exposed — is that the framework's genuine insight (tools have gradients; the default shapes you; gatekeep at the boundary) is entangled with a dispositional anti-modernism (the romance of the pre-digital, the suspicion of comfort and convenience as such) that comes from the same source. The gradient-insight is shared by serious, non-reactionary tech critics (Postman, the attention-economy critique); the anti-comfort tilt is the framework's own and is what pulls the test toward Luddism. The honest synthesis keeps the gradient-insight (which has good company) and explicitly resists the anti-comfort tilt (which is the framework's prejudice) by demanding the discernment that distinguishes corrosive design from mere ease. The vault's verdict: a genuinely useful decision-protocol carrying a reactionary disposition, and the disposition is the part that has to be checked at the gate alongside the tools.

Cross-Domain Handshakes

Rubber-duck version: the test is the perimeter applied to tools, so it handshakes into that cosmology (cross-domain), the sovereignty it protects (cross-domain), and its AI-specific application (business).

  • Cross-Domain: Perimeter as Sacred Boundary — the test IS the perimeter applied to technology. What's identical: both gatekeep what crosses a sacred boundary. What differs: a tool's "crossing" is gradual and habituating (it shapes you over years) rather than a single admission, so the perimeter-test for technology has to reckon with the gradient, not just the gate. The insight: technology is the case that most reveals why the perimeter matters — because what you admit doesn't stay what it was when you admitted it; it trains you, which is exactly why the decision belongs at the boundary.

  • Cross-Domain: Sovereignty & Self-Authorship — the value the test protects. What the handshake produces: question two (sovereignty or dependency) is the sovereignty-trait applied to tools — the recognition that a platform you depend on and don't control is a sovereignty you've ceded, and that much of modern dependency is technological. The test is sovereignty's gatekeeper at the digital boundary.

  • Business: AI Ethics — Solar Framework — the AI-specific application of the same five questions. What the parallel unlocks: AI is the test's hardest case, because it most directly offers to do your thinking (the deepest capacity-atrophy risk) while most directly extending capability (the strongest strength-case) — so the same five questions produce the sharpest strength-vs-weakness and sovereignty-vs-dependency tensions on AI of any technology, which is why the AI application warrants its own page running this test specifically.

The Live Edge

The sharpest implication. The framework is right that "technology is neutral, it's all how you use it" is a comfortable lie — tools have gradients, the gradient trains you, and you will not win the daily heroic fight against a gradient you let inside, so the decision that matters is at the gate. That's a genuinely sharp insight, and the five questions make it concrete in a way most tech-ethics doesn't. But the destabilizing edge cuts both ways. Against the user: most of the tools you never decided to admit — the phone, the feeds, the always-on — fail the test badly on sovereignty, attention, and perimeter, which means you're being trained, daily, by gradients you'd reject if you ran them at the gate, and the honest verdict is uncomfortable. And against the framework: the same test, run with the framework's anti-comfort tilt, becomes a machine for rejecting everything new as dissolution — nostalgia with a rubric — and the line between the test-as-wisdom and the test-as-Luddism is whether it can ever say yes to the genuinely new. So the live edge is a discipline pointed in both directions: run the five questions honestly enough to admit how much you're already being trained by tools you never chose, and honestly enough that the test can still say yes to the new tool that genuinely builds you — because a gate that never opens isn't sovereignty, it's a different kind of cage.

Generative questions:

  • Which tools in your life would you reject if you ran them at the gate today? The ones that arrived without a decision — the phone, the feeds. The test's first uncomfortable yield is how much you're being trained by gradients you never chose.
  • Can your test say yes to the new? If every novel tool fails, you're running Luddism, not discernment. What's the new tool the honest test admits — and if there isn't one, what does that reveal about your test?
  • Is the anti-solar gradient in the tool or in your default use — and can you reverse it? The discernment-question. A bad-gradient tool admitted with the right disciplines can flip; admitted without them, you slide down exactly the gradient you identified.

Connected Concepts

Footnotes

domainBehavioral Mechanics
developing
sources1
complexity
createdJun 2, 2026
inbound links5