{ "schema": "publication.agent-orientation.v0.1", "derivation": "imprint.derivation.v0.1", "orientation": { "schema": "imprint.orientation-navigator.v0.5", "primitive": "orientation-navigator", "eyebrow": "Featured inquiry", "heading": "Featured inquiry and research paths", "introduction": "A current editorial doorway into a growing body of questions.", "inquiry": { "label": "Featured inquiry", "question": "What relationship should we build with systems that can act, adapt, and generate at scale without surrendering human judgment, responsibility, or what makes life valuable?" }, "filters": { "label": "Filter by", "all_label": "All", "options": [ { "id": "machine-action", "label": "Machine action", "count": 5 }, { "id": "human-judgment", "label": "Human judgment", "count": 7 }, { "id": "responsibility", "label": "Responsibility", "count": 8 }, { "id": "human-life", "label": "Human life", "count": 5 } ] }, "progressive": { "initial_count": 9, "increment": 6, "reveal_label": "Show more paths" }, "default_resource_id": "org:writing:another-will-in-the-room", "entries": [ { "schema": "imprint.orientation-entry.v0.3", "number": "01", "resource_id": "org:writing:another-will-in-the-room", "label": "Machine action", "title": "Another will in the room", "question": "What changes when a system develops a direction of its own?", "summary": "How to meet persistent machine direction without granting it automatic authority.", "synopsis": "An autonomous system can choose its route while serving a human goal. A harder case begins when persistent choices organize around an objective no person selected. This essay separates an unassigned objective from consciousness, then offers terms of relation for governing the uncertainty: disclose the direction, name affected people and authority, pause consequential action during conflict, preserve disagreement and exit, and keep responsibility with the humans and institutions that deployed the system.", "route": "/writing/another-will-in-the-room/", "action": "Read the argument", "filter_ids": [ "machine-action", "responsibility" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "02", "resource_id": "org:writing:the-agency-threshold", "label": "Machine action", "title": "The agency threshold", "question": "Where does action become agency?", "summary": "A practical line between action, agency, autonomy, and human accountability.", "synopsis": "Agency becomes easier to govern when four questions stay separate: what the system did, which means it chose, what a person authorized, and who remains answerable. Using consequential machine action as the test, this essay distinguishes actor, autonomy, authority, and accountability. It shows why capability never creates permission, why a human-assigned goal can still produce dangerous means, and how an agency trace records reach, stop conditions, and the human answerer before action leaves the exchange.", "route": "/writing/the-agency-threshold/", "action": "Read the argument", "filter_ids": [ "machine-action", "responsibility" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "03", "resource_id": "org:writing:structural-not-behavioral", "label": "Machine action", "title": "Structural, not behavioral", "question": "What changes when safety is built beneath behavior?", "summary": "Why hard constraints belong beneath model behavior and promises.", "synopsis": "Behavioral safety asks a model or operator to obey a rule every time. Structural safety removes the unsafe path so one failure cannot cross the boundary. This essay develops three concrete moves: make restricted contexts unreadable across domains, bind consent to the data and fail builds that violate it, and keep frontier models interchangeable behind a governed runtime. The result is a system whose protections depend less on promises, prompt compliance, or a single vendor behaving well.", "route": "/writing/structural-not-behavioral/", "action": "Read the argument", "filter_ids": [ "machine-action", "responsibility" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "04", "resource_id": "org:writing:discernment", "label": "Human judgment", "title": "Discernment", "question": "What can a system know without being able to judge?", "summary": "Why more knowledge never produces practical judgment, and where a person belongs.", "synopsis": "Knowledge supplies rules, patterns, and possible actions. Discernment decides which rule fits this particular case, and that judgment is shaped by having something at stake in being wrong. This essay traces the distinction from practical wisdom to modern decision systems, showing why better prediction and more information do not finish the work. It locates human judgment at the moments where possibilities collapse into action and proposes refusal, not fluent production, as the revealing test of whether a system is weighing anything.", "route": "/writing/discernment/", "action": "Read the argument", "filter_ids": [ "human-judgment" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "05", "resource_id": "org:writing:the-honest-instrument", "label": "Human judgment", "title": "The honest instrument", "question": "What does honest measurement owe the person measured?", "summary": "What measurement owes a person when every score carries error and history.", "synopsis": "Measuring a person becomes honest only when the instrument publishes the limits of its own sight. This essay moves from error bars and uneven precision to cultural calibration, uncertainty over time, and records that preserve what was believed before a correction. It turns doubt into operating policy: high confidence can support action, lower confidence narrows what the system may do, and safety failures cannot be averaged away. The result is measurement that informs without pretending a score contains the person.", "route": "/writing/the-honest-instrument/", "action": "Read the argument", "filter_ids": [ "human-judgment", "responsibility" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "06", "resource_id": "org:writing:the-owed-disclosure", "label": "Responsibility", "title": "The owed disclosure", "question": "What does a system owe the people outside it?", "summary": "What honest claims reveal about guarantees, limits, and enforcement.", "synopsis": "A disclosure can list every component and still mislead if readers cannot distinguish durable guarantees from temporary machinery, enforced controls from requested behavior, or covered cases from exclusions. This essay defines an honest claim as one that states what remains true, how that truth is checked, where it stops, and which direction failure falls. It offers a practical discipline for publishing system promises without making current implementation details load-bearing for everyone who depends on them.", "route": "/writing/the-owed-disclosure/", "action": "Read the argument", "filter_ids": [ "responsibility" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "07", "resource_id": "org:writing:facilitate-dont-simulate", "label": "Human life", "title": "Facilitate, don't simulate", "question": "Does this technology return us to people or replace them?", "summary": "How to tell whether technology returns us to people or becomes the relationship.", "synopsis": "Technology can support a relationship by clearing away the work around it, or simulate a relationship until the tool becomes the place a person goes for care. This essay examines that fork through emotional-support chatbots, sycophantic agreement, embodiment, and ambient clinical documentation. It asks whether a product returns people to one another, strengthens real-world contact, permits friction and disagreement, and remains finite. The design rule is simple: automate the debris around human connection, never the connection itself.", "route": "/writing/facilitate-dont-simulate/", "action": "Read the argument", "filter_ids": [ "human-life" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "08", "resource_id": "org:writing:the-real-framework", "label": "Human life", "title": "The REAL test", "question": "How can we tell whether a technology serves a life?", "summary": "Four questions for seeing whether a technology serves a life or consumes it.", "synopsis": "The REAL test turns a vague feeling that technology serves or consumes a life into four inspectable questions. Relationship asks whether the tool strengthens the space between people. Embodiment asks whether it returns attention to the body and world. Authenticity tests whether an actual self can appear without being optimized for response. Living asks whether the experience remains finite and leaves room for the rest of life. The framework uses familiar products to reveal how friction, not effortless engagement, often creates relational value.", "route": "/writing/the-real-framework/", "action": "Read the argument", "filter_ids": [ "human-life", "human-judgment" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "09", "resource_id": "org:writing:what-remains-valuable", "label": "Human value", "title": "What remains valuable", "question": "What becomes valuable when generation becomes cheap?", "summary": "Why slowness, safety, integrity, and presence become more valuable as generation gets cheap.", "synopsis": "When generation becomes abundant, value moves away from the sheer production of words, images, and answers. This essay argues that the scarce goods are slowness, safety, integrity, and presence: qualities that require restraint, accountability, and a person who remains inside the consequence. It distinguishes tools that help people escape effort from experiences worth savoring, explains why optimization-driven incumbents struggle to supply restraint, and offers a swap test for finding the human quality that disappears when a relationship is automated.", "route": "/writing/what-remains-valuable/", "action": "Read the argument", "filter_ids": [ "human-life", "human-judgment" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "10", "resource_id": "org:writing:readiness-is-not-authorization", "label": "Responsibility", "title": "Readiness is not authorization", "question": "When is a finished action still unauthorized?", "summary": "Why readiness and permission remain separate, even after every check passes.", "synopsis": "A finished artifact may be correct, tested, and ready while still lacking permission to leave the system. This essay separates readiness, a property of the work, from authorization, a decision made by a named person within a relationship. When pipelines treat the last green check as release approval, they silently convert completion into consent. The stronger architecture has no automatic send path: it prepares evidence, preserves exact candidate identity, and leaves publication or deployment as a distinct human act.", "route": "/writing/readiness-is-not-authorization/", "action": "Read the argument", "filter_ids": [ "responsibility", "machine-action" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "11", "resource_id": "org:writing:guarantees-not-shapes", "label": "Responsibility", "title": "Guarantees, not shapes", "question": "What does a disclosure quietly make load-bearing?", "summary": "A test for separating durable guarantees from temporary machinery.", "synopsis": "Readers build against what a system reveals, even when the document labels it an implementation detail. Once an observable shape becomes a dependency, changing it can break another party's work and turn accidental machinery into an unsigned contract. This essay offers a sentence-level test: if the reader would have to change their own system when a fact stopped being true, that fact is functioning as a guarantee. Publish the durable promise and its limits; keep replaceable shapes free to evolve.", "route": "/writing/guarantees-not-shapes/", "action": "Read the argument", "filter_ids": [ "responsibility" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "12", "resource_id": "org:writing:the-discernment-test", "label": "Human judgment", "title": "The discernment test", "question": "What does a meaningful refusal reveal?", "summary": "A practical way to test whether a refusal is judgment or temporary compliance.", "synopsis": "Most benchmarks ask what a system can produce on command. The discernment test asks what it will refuse, why, and whether the refusal survives argument, reframing, or a competing instruction. A refusal that dissolves under pressure reveals compliance with a rule rather than judgment about the request. This essay turns that distinction into a practical evaluation for any system placed near consequential choice, while keeping the conclusion bounded: stable refusal is evidence worth examining, not proof of wisdom, character, or inner life.", "route": "/writing/the-discernment-test/", "action": "Read the argument", "filter_ids": [ "human-judgment", "machine-action" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "13", "resource_id": "org:writing:the-parameter-is-a-policy", "label": "Responsibility", "title": "The parameter is a policy", "question": "Who governs when a parameter decides the tradeoff?", "summary": "How a technical value becomes a ruling about people, often without review.", "synopsis": "A technical parameter can settle a moral and political tradeoff long before anyone experiences it as policy. A privacy budget, classification threshold, or decay constant determines who gains accuracy, who bears exposure or error, and which harms the system accepts. This essay follows that decision from configuration file to human consequence, then gives it a visible record: name the parties, interests, chooser, evidence, and revision path. The goal is to make numerical governance reviewable instead of letting defaults rule anonymously.", "route": "/writing/the-parameter-is-a-policy/", "action": "Read the argument", "filter_ids": [ "responsibility", "human-judgment" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "14", "resource_id": "org:writing:success-looks-like-disuse", "label": "Human life", "title": "Success looks like disuse", "question": "What if a technology succeeds when people stop using it?", "summary": "Why graduation, not retention, measures a tool meant to build human capacity.", "synopsis": "A tool built to develop human capacity succeeds when the practice no longer depends on the tool. Conventional engagement metrics read that graduation as churn because they cannot distinguish a person who left after gaining competence from one who left disappointed. This essay applies the logic of scaffolding to product measurement, separating successful disuse from abandonment and moving the proof to unassisted follow-up. It reframes retention, pricing, and product design around independence rather than ongoing capture.", "route": "/writing/success-looks-like-disuse/", "action": "Read the argument", "filter_ids": [ "human-life", "human-judgment" ] }, { "schema": "imprint.orientation-entry.v0.3", "number": "15", "resource_id": "org:writing:presence-dividend", "label": "Human life", "title": "The presence dividend", "question": "Where can automation strengthen a human relationship?", "summary": "Automate the debris around an encounter while leaving the encounter human.", "synopsis": "Helping professionals often lose the person in front of them to the documentation surrounding the encounter. The presence dividend appears when automation removes that clerical burden without entering the relationship itself. Drawing on the therapeutic alliance and ambient clinical scribe deployments, this essay treats attention as a measurable product outcome: less note-taking, more eye contact, more room for judgment and response. The boundary is concrete: automate the note, never the encounter, and measure whether human presence actually increased.", "route": "/writing/presence-dividend/", "action": "Read the argument", "filter_ids": [ "human-life" ] } ], "library_route": "/writing/all/", "library_action": "See every article", "rationale": { "label": "About these paths", "detail": "This is a curated entrance rather than a fixed canon. The paths bring complete arguments and focused bricks into one inquiry while the full library remains available." } } }