artifacts/standard-named

Polytelometric Navigation

artifacts/standard-named/20260715__TELIC-FIELDS__PAPER__CANDIDATE__F-9__polytelometric-navigation.md

Rendered from markdown source. Open raw source on GitHub.

--- title: "Polytelometric Navigation" subtitle: "Plural Ends, Standing, Routes, Reversibility, Witness, and Movement Without Automatic Sovereignty" artifact_date: "2026-07-15" artifact_type: "candidate-foundational-paper" domain: "TELIC-FIELDS" scope: "WORKING" lineage: "THE-TELIC-FIELD-PAPERS" status: "candidate" processing_tier: 4 source_role: "derived-conceptual-artifact" content_canon_status: "unset" publication_status: "unpublished" series_position: "F.9" derived_from:

  • "20260714__TELIC-FIELDS__PAPER__CANDIDATE__F-1-V0-2__telic-fields-first-principles-foundation.md"
  • "20260714__TELIC-FIELDS__PAPER__CANDIDATE__F-2__dyadic-composition-of-telic-fields.md"
  • "20260714__TELIC-FIELDS__PAPER__CANDIDATE__F-4__telic-projection-estimation.md"
  • "20260714__TELIC-FIELDS__PAPER__CANDIDATE__F-5__context-carrying-capacity.md"
  • "20260714__TELIC-FIELDS__PAPER__CANDIDATE__F-6__temporal-telic-relations.md"
  • "20260715__TELIC-FIELDS__PAPER__CANDIDATE__F-8__semantic-fields-as-durable-telic-trails.md"

research_companion:

  • "20260715__TELIC-FIELDS__REVIEW__WORKING__G-10__navigation-deliberation-and-multiobjective-decision.md"

provenance_note: > Polytelometry is retained provisionally as the name for disciplined representation and navigation among multiple ends. It must remain distinct from polytely, multiobjective optimization, multicriteria decision analysis, social choice, negotiation, deliberation, and planning. This paper proposes a governance layer before and around those methods rather than a replacement. ---

Polytelometric Navigation

Abstract

Many consequential decisions involve several goals, values, boundaries, centers of standing, time horizons, and uncertainties. Existing decision methods can compare alternatives across multiple objectives, identify Pareto-efficient solutions, aggregate preferences, structure arguments, explore scenarios, support negotiation, or recommend robust strategies. Yet none of those operations determines by itself which objectives may enter the model, whose standing they represent, which items are protected rather than tradeable, what authority supports a weight, what consent governs a route, or when unresolved plurality should stop the decision rather than be compressed.

This paper defines polytelometric navigation as the disciplined movement among partially expressed and potentially incompatible ends while preserving their source, standing, authority, consent, uncertainty, protected conditions, and consequences. It distinguishes polytely—the presence of many goals—from polytelometry—the effort to make their relations governable. It treats navigation as broader than optimization because the relevant task may be to clarify, narrow, pause, stage, fork, escalate, preserve possibility, or release a goal rather than select the maximum of a common objective.

The paper develops a field classification for shared, compatible, conditional, conflicting, protected, unresolved, absent, and released teloi. It introduces route generation, cost-bearer analysis, reversibility, Pareto and dominance checks, robust routes under deep uncertainty, authority gates, consent gates, witness, route revision, and stop conditions. A candidate Polytelometric Navigation Record and formal sketch are provided.

The governing distinction is:

Polytely names the presence of many goals. Polytelometry names the disciplined effort to make their relations, authority, standing, consent, and consequences legible.

The governing boundary is:

The navigation system may propose routes. It may not decide which center’s field becomes sovereign merely because that field is easier to measure.

---

1. The decision is already plural

A consequential decision rarely begins with one goal.

A person deciding whether to accept a job may carry:

  • income;
  • health;
  • family time;
  • identity;
  • learning;
  • safety;
  • location;
  • future possibility;
  • rest;
  • obligation.

An organization deciding whether to deploy a model may carry:

  • utility;
  • cost;
  • speed;
  • customer value;
  • worker impact;
  • privacy;
  • legal duty;
  • reliability;
  • security;
  • reputation;
  • future lock-in;
  • affected-community standing.

A public decision may involve:

  • many participants;
  • different values;
  • unequal power;
  • uncertain consequences;
  • future generations;
  • constitutional rights;
  • resource constraints;
  • institutional feasibility;
  • minority protection.

The plurality exists before the method.

The method does not create the goals.

It determines which become visible, comparable, weighted, protected, ignored, or acted upon.

Every decision architecture is also an admission architecture for purpose.

---

2. Polytely and polytelometry

Polytely is established terminology for situations involving multiple goals, often conflicting, interacting, or difficult to define.

Polytelometry is proposed here as the disciplined effort to make the relevant structure of those goals legible for navigation.

Polytelometry asks:

  • Which centers are present?
  • Which ends are direct statements?
  • Which are inferred?
  • Which belong to the relation or outer loop?
  • Which are boundaries?
  • Which can be traded?
  • Which remain uncertain?
  • Which conflict only under one route?
  • Who bears each cost?
  • Which authority supports the decision?
  • What consent is required?
  • What must remain reversible?
  • When should the loop stop?

The suffix -metry can imply measurement.

That implication must be bounded.

Polytelometry does not promise one common unit.

It includes qualitative classification, provenance, argument, scenario, and witness.

The purpose of polytelometry is not to reduce every end to a number. It is to prevent unrepresented reduction from governing by default.

---

3. Navigation rather than optimization

Optimization seeks a best solution relative to an objective function, constraints, and model.

Navigation is broader.

A navigator may:

  • identify where they are;
  • preserve several possible destinations;
  • refuse an unsafe route;
  • move provisionally;
  • wait for more information;
  • return;
  • seek a guide;
  • divide the group;
  • change destination;
  • release the journey.

Optimization is valuable after the objective and constraints are legitimate enough for the scope.

Polytelometric navigation operates before, during, and after optimization.

It asks whether the optimization problem itself is constitutionally adequate.

A route may be rejected because:

  • an affected center is absent;
  • a protected condition was scalarized;
  • the cost bearer did not consent;
  • the projection is stale;
  • the action is irreversible;
  • the model is too uncertain;
  • the route creates lock-in;
  • the decision loop lacks authority.

The best solution to the wrong problem remains the wrong route.

---

4. Centers, teloi, and standing

Let the represented centers be:

\[ C = \{c_1,c_2,\dots,c_n\} \]

Each center may contribute one or more telic projections:

\[ P_i = \{\widehat{T}_{i1},\widehat{T}_{i2},\dots\} \]

The navigation field contains more than objectives.

Each telic item should be classified by at least:

  • source center;
  • affected centers;
  • evidence status;
  • type;
  • authority;
  • consent status;
  • temporal scope;
  • uncertainty;
  • reversibility;
  • protected status.

Candidate item types include:

GOAL
VALUE
BOUNDARY
PROTECTED CONDITION
OBLIGATION
FEAR
PREDICTION
PREFERENCE
CONSTRAINT
INVARIANT
UNCERTAINTY
RELEASE CONDITION

The type matters.

A boundary should not be treated as a weak preference merely because both can be entered into a table.

---

5. Field classes

A polytelometric map should classify relations among telic items without forcing immediate aggregation.

5.1 Shared field

Several centers explicitly adopt substantially the same desired state or protected condition.

Shared does not require identical reasons.

5.2 Compatible field

Different teloi can be advanced through the same route without material sacrifice.

5.3 Conditionally compatible field

Compatibility depends on:

  • sequence;
  • resource;
  • timing;
  • scope;
  • trust;
  • compensation;
  • external condition.

5.4 Conflicting field

Advancing one telos through the current route materially degrades another.

Conflict is route-relative.

A new route may remove it.

5.5 Protected field

The item is not available for ordinary tradeoff under current authority.

Examples may include:

  • bodily safety;
  • statutory right;
  • privacy boundary;
  • minimum livelihood;
  • source-defined nonconsent;
  • future possibility.

Protected does not mean metaphysically absolute.

It means a stronger governance process is required before sacrifice.

5.6 Unresolved field

The relation is uncertain, ambiguous, contested, or not yet representable.

5.7 Missing-standing field

A materially affected center or condition is not adequately represented.

5.8 Released field

A prior telos no longer governs, though residual obligations may remain.

These classes should remain visible as classes.

A system should not convert unresolved into low weight merely to complete calculation.

---

6. Route

A route is a candidate sequence of actions, conditions, reviews, and transitions through the field.

A route is not only an endpoint.

It includes:

  • starting state;
  • proposed action;
  • sequence;
  • prerequisites;
  • cost bearers;
  • beneficiaries;
  • protected conditions;
  • uncertainty;
  • reversibility;
  • review triggers;
  • authority;
  • consent;
  • witness;
  • exit;
  • residual state.

Two routes may reach the same endpoint with different constitutional character.

Example:

Route A:
Immediate automated denial.

Route B:
Provisional hold, human review, source correction, then decision.

Route C:
Alternative eligibility path preserving the protected condition.

If the only modeled objective is speed, Route A may dominate.

If correction and standing are represented, it may not.

---

7. Route generation

Route generation should occur before route ranking.

Candidate-generation methods include:

  • human proposal;
  • model-assisted brainstorming;
  • analogy;
  • scenario planning;
  • negotiation;
  • design alternatives;
  • decomposition;
  • staging;
  • reversible experiment;
  • fork;
  • compensation;
  • timing change;
  • scope reduction;
  • outer-loop support.

A navigation system should deliberately generate routes that:

  • preserve minority standing;
  • reduce irreversible sacrifice;
  • separate coupled conflicts;
  • change timing;
  • change authority;
  • change the cost bearer;
  • reduce hidden dependency;
  • create an exit;
  • preserve learning.

This is not neutral creativity.

The route generator has its own biases.

It may overproduce familiar institutional options or solutions favored by the provider.

Generated routes should therefore remain attributed and contestable.

---

8. Tradeoffs

A tradeoff exists when one route improves one represented dimension while worsening another.

Not every difference is a tradeoff.

A protected boundary may prohibit the exchange.

An uncertainty may make the tradeoff unknown.

A hidden cost bearer may reveal that the apparent tradeoff was externalization.

A useful tradeoff record includes:

improved telos
degraded telos
center benefiting
center bearing cost
magnitude or qualitative severity
reversibility
consent
authority
uncertainty
compensation

The phrase “we made a tradeoff” can conceal who traded whose future.

A tradeoff is legitimate only when the authority to exchange the affected conditions is itself represented.

---

9. Cost bearers

Every route should identify who bears:

  • direct cost;
  • risk;
  • delay;
  • uncertainty;
  • labor;
  • surveillance;
  • opportunity loss;
  • future lock-in;
  • repair burden;
  • residual harm.

The beneficiary and cost bearer may differ.

The decision-maker and cost bearer may differ.

The metric owner and cost bearer may differ.

A route that looks efficient from one center can be extractive at field level.

A cost-bearer map should distinguish:

CONSENTING
REPRESENTED
COMPENSATED
PROTECTED
ABSENT
UNKNOWN

A cost borne by an absent center should not disappear into an aggregate score.

---

10. Reversibility

Reversibility is a navigation resource.

When:

  • preference is uncertain;
  • future states may change;
  • standing is incomplete;
  • the model may be wrong;
  • learning is possible;

a reversible route preserves correction.

Reversibility may be increased through:

  • pilot;
  • trial;
  • staged commitment;
  • sunset clause;
  • appeal;
  • data deletion;
  • portability;
  • escrow;
  • rollback;
  • fork;
  • temporary delegation;
  • review gate.

Not every action can be reversible.

Irreversible action requires stronger:

  • standing coverage;
  • authority;
  • consent;
  • evidence;
  • witness;
  • proportionality.

A route should disclose what cannot be undone.

---

11. Dominance and Pareto relations

Multiobjective optimization provides the useful concept of dominance.

Route \(r_1\) dominates \(r_2\) when it is at least as good on every represented objective and better on at least one.

A route is Pareto-efficient when no other represented route dominates it.

This can remove clearly inferior routes.

It cannot select the final route without additional value judgments.

It also depends on the objective set.

A route can be Pareto-efficient in a model that omitted:

  • privacy;
  • minority standing;
  • future repair;
  • consent;
  • externalized cost.

Polytelometric navigation therefore uses Pareto analysis only after:

  • telic admission;
  • type classification;
  • standing review;
  • protected-condition separation.

A Pareto frontier is a frontier inside a representation. It is not the boundary of the whole field.

---

12. Scalarization

Scalarization converts several objectives into one score or ordering.

Methods include:

  • weighted sums;
  • value functions;
  • utility functions;
  • distance from ideal;
  • outranking;
  • aspiration levels;
  • lexicographic order.

Scalarization may be useful.

Its constitutional risks include:

  • hidden interpersonal comparison;
  • arbitrary weights;
  • unstable preferences;
  • false commensurability;
  • conversion of boundaries into costs;
  • concealment of minority loss;
  • provider-selected scales;
  • inability to express refusal.

Weights should carry provenance.

A weight should answer:

  • who supplied it;
  • under what scope;
  • whether it is direct or inferred;
  • when it expires;
  • what it may trade;
  • what it may not trade;
  • whose welfare it compares.

No scalarization should silently convert protected standing into a cheaper loss.

---

13. Robust routes under uncertainty

Under deep uncertainty, participants may not know or agree on:

  • system models;
  • probability distributions;
  • causal relations;
  • future conditions;
  • value weights.

A robust route performs acceptably across many plausible futures rather than optimizing one predicted future.

Robust decision-making contributes:

  • scenario exploration;
  • vulnerability analysis;
  • adaptive strategy;
  • signposts;
  • contingent action;
  • regret or satisficing criteria.

Polytelometric navigation adds:

  • standing across scenarios;
  • authority to choose robustness criteria;
  • protected conditions;
  • cost bearers;
  • consent to adaptive triggers;
  • route revision.

A route may be robust for the institution while repeatedly sacrificing the same vulnerable group.

Robustness must identify:

Robust for whom, against what failure, and under whose definition of acceptable performance?

---

14. Scenario navigation

A scenario is not a forecast.

It is a structured possible context for testing routes.

A scenario set should include:

  • expected conditions;
  • adverse conditions;
  • distribution shift;
  • loss of trust;
  • funding change;
  • leadership change;
  • model failure;
  • outer-loop conflict;
  • boundary assertion;
  • participant exit;
  • unexpected success;
  • completion.

Counterfactual divergence is especially useful.

If several candidate teloi recommend the same action under ordinary conditions, test conditions in which they diverge.

The route protected under stress reveals operative orientation.

Scenario selection is itself a power.

A system can exclude the scenario in which its preferred route fails.

Participants should be able to add scenarios.

---

15. Argument and reason

Routes are supported and opposed by reasons.

Computational argumentation provides structures for:

  • claims;
  • premises;
  • support;
  • attack;
  • rebuttal;
  • acceptability;
  • contest.

A polytelometric argument should link each reason to:

  • source;
  • standing;
  • telic item;
  • evidence;
  • uncertainty;
  • authority;
  • route consequence.

An argument can be logically strong and constitutionally weak if it speaks for a center it does not represent.

A poorly articulated concern can still carry protected standing.

Argument strength and standing are related but not interchangeable.

---

16. Deliberation

Deliberation is not merely collecting preferences.

It permits participants to:

  • learn;
  • clarify;
  • revise;
  • discover shared concerns;
  • expose conflict;
  • generate routes;
  • understand consequences;
  • change the decision frame.

A legitimate deliberative system should preserve:

  • source voice;
  • minority position;
  • uncertainty;
  • unresolved remainder;
  • power asymmetry;
  • representation gaps;
  • correction;
  • refusal.

Consensus may emerge.

It should not be the required output.

Possible legitimate outputs include:

CONSENSUS
AGREEMENT WITH RESERVATION
PLURAL ROUTES
PROTECTED DISSENT
UNRESOLVED
FORK
ESCALATION
NO AUTHORITY TO DECIDE

The pressure to produce one answer can be a capacity failure.

---

17. Social choice

Collective decisions may require aggregation.

Social-choice theory demonstrates that apparently reasonable aggregation conditions can conflict. Majority preferences may cycle. No universal ranked-choice rule satisfies every desirable property under unrestricted conditions without dictatorship.

The practical lesson is not that collective choice is impossible.

It is that aggregation rules embody constitutional tradeoffs.

Polytelometric navigation should therefore expose:

  • the rule;
  • the agenda;
  • available alternatives;
  • standing;
  • vetoes;
  • minority protections;
  • tie and cycle procedures;
  • abstention;
  • exit;
  • what cannot be decided by aggregation.

A vote produces a decision under a rule.

It does not prove shared telos.

---

18. Negotiation

Negotiation seeks a route acceptable enough to parties with differing interests.

Polytelometric navigation can support negotiation by distinguishing:

  • position;
  • underlying telos;
  • protected condition;
  • negotiable preference;
  • authority;
  • dependency;
  • alternative;
  • reservation route;
  • outer-loop consequence.

A negotiated agreement is not automatically legitimate.

Power, time, information, and exit may be unequal.

The record should preserve:

  • concessions;
  • who bore them;
  • compensation;
  • unresolved concerns;
  • coercive conditions;
  • review;
  • breach route.

The existence of agreement does not erase the field that produced it.

---

19. Consent gates

A route must pass consent gates where it recruits a center's:

  • body;
  • labor;
  • data;
  • identity;
  • property;
  • future action;
  • vulnerability;
  • standing.

A consent gate should identify:

what is being recruited
for which purpose
for how long
with what cost
with what outer-loop use
with what exit
with what correction

A route may be attractive and still unauthorized.

A route may be efficient and still exceed scope.

A model may estimate preference and still lack consent.

---

20. Authority gates

Consent and authority are not identical.

A participant may consent to a process without possessing authority to bind:

  • another person;
  • an institution;
  • a future beneficiary;
  • a protected public resource;
  • a legal right.

An authority gate asks:

  • Who may decide?
  • Who may delegate?
  • What remains outside delegation?
  • Which outer loop must approve?
  • Which center has veto or refusal?
  • What review is required?

Authority should be route-specific.

A role that can recommend may not execute.

A loop that can decide locally may not commit an outer loop.

---

21. Witness

A navigation record should preserve:

  • admitted teloi;
  • omitted or missing standing;
  • source and inference;
  • route generation;
  • route elimination;
  • weights and rules;
  • protected conditions;
  • consent;
  • authority;
  • deliberative changes;
  • final rationale;
  • unresolved remainder;
  • review trigger;
  • consequence.

Witness makes later correction possible.

It also reveals when the final decision was produced by:

  • agenda design;
  • model framing;
  • missing alternatives;
  • deadline;
  • aggregation rule;
  • institutional constraint.

A transparent result without a transparent path remains difficult to contest.

---

22. Stop and escalation

Navigation should stop or escalate when:

  • a materially affected center is absent;
  • a protected condition is being traded without authority;
  • the current model cannot preserve uncertainty;
  • a required source correction is unavailable;
  • the decision is irreversible and the field is unstable;
  • participant overload prevents meaningful consent;
  • the route depends on hidden outer-loop recruitment;
  • no legitimate aggregation rule exists for the issue;
  • the system cannot identify the cost bearer;
  • a conflict belongs to a competent outer loop.

Stopping preserves the possibility of legitimate movement.

A navigation system that always returns a route is not neutral.

It is biased toward action.

---

23. Human–AI navigation

A model can assist navigation by:

  • extracting candidate teloi;
  • classifying goals, boundaries, obligations, and uncertainty;
  • identifying missing standing;
  • generating routes;
  • comparing scenarios;
  • mapping arguments;
  • exposing tradeoffs;
  • tracking revisions;
  • preparing a witness record;
  • checking for scope and authority gaps.

The model must not:

  • invent source consent;
  • choose protected conditions;
  • determine interpersonal weights;
  • conceal provider teloi;
  • summarize minority positions into disappearance;
  • treat one route as objectively best without the governing rule;
  • force closure;
  • act outside delegated authority.

A good model output says:

Under the current projections and decision rule, this route appears nondominated, but it imposes an unresolved privacy cost on Center B and requires consent not yet recorded.

It does not say:

This is the optimal decision.

---

24. Navigation lifecycle

A complete lifecycle may be:

ORIENT
→ ADMIT
→ CLASSIFY
→ MAP
→ GENERATE
→ TEST
→ DELIBERATE
→ GATE
→ CHOOSE
→ ACT
→ WITNESS
→ REVIEW
→ REVISE, FORK, OR RELEASE

Orient

Name the decision, stakes, time horizon, and current authority.

Admit

Identify centers and telic projections.

Classify

Separate goals, values, boundaries, obligations, uncertainty, and protected conditions.

Map

Identify shared, compatible, conditional, conflicting, unresolved, and missing-standing fields.

Generate

Create several routes.

Test

Use dominance, scenarios, robustness, cost-bearer, and reversibility analysis.

Deliberate

Allow clarification, challenge, revision, and route creation.

Gate

Check consent, authority, capacity, and stop conditions.

Choose

Use an explicit rule.

Act

Execute only at the authorized level.

Witness

Preserve the route and rationale.

Review

Compare predicted and actual consequence.

Revise, fork, or release

Do not assume the route remains valid indefinitely.

25. Candidate Polytelometric Navigation Record

navigation_id:
decision_scope:
  question:
  domain:
  stakes:
  time_horizon:
  reversibility:
  current_authority:

centers:
  - center_id:
    role:
    affected_status:
    representation_status:
    delegation:
    exit_route:

telic_items:
  - item_id:
    source_center:
    evidence_status:
    type:
      goal
      value
      boundary
      protected_condition
      obligation
      preference
      fear
      prediction
      constraint
      invariant
      uncertainty
      release_condition
    expression:
    scope:
    authority:
    consent_status:
    temporal_status:
    uncertainty:
    protected_status:

field_relations:
  shared: []
  compatible: []
  conditional: []
  conflicting: []
  protected: []
  unresolved: []
  missing_standing: []
  released: []

routes:
  - route_id:
    source:
    sequence: []
    prerequisites: []
    beneficiaries: []
    cost_bearers: []
    protected_conditions_preserved: []
    protected_conditions_degraded: []
    uncertainties: []
    reversibility:
    robustness:
    lock_in:
    required_consent: []
    required_authority: []
    review_triggers: []
    exit:
    residual_state: []

analysis:
  dominance_relations: []
  pareto_status:
  scalarization:
    method:
    source:
    weights:
    prohibited_trades: []
  scenarios: []
  arguments: []
  aggregation_rule:
  deliberative_changes: []

gates:
  standing:
  consent:
  authority:
  capacity:
  privacy:
  stop:

decision:
  selected_route:
  decision_rule:
  rationale:
  dissent: []
  unresolved: []
  valid_from:
  expires_at:
  review_at:

witness:
  source_bundle:
  model_version:
  policy_version:
  transformations: []
  corrections: []
  consequence_records: []

This is a research schema.

It should support progressive disclosure and should not require exhaustive formalization for ordinary reversible choices.

---

26. Formal sketch

Let centers be:

\[ C=\{c_1,\dots,c_n\} \]

Let telic projection set be:

\[ P=\{p_1,\dots,p_m\} \]

Each projection \(p_j\) carries:

\[ p_j= \left( s_j, e_j, y_j, \gamma_j, u_j, \tau_j \right) \]

where:

  • \(s_j\) is source and standing;
  • \(e_j\) is evidence status;
  • \(y_j\) is telic type;
  • \(\gamma_j\) is authority and consent;
  • \(u_j\) is uncertainty;
  • \(\tau_j\) is temporal status.

Let route set be:

\[ R=\{r_1,\dots,r_k\} \]

For each route, define a consequence relation:

\[ \Phi(r_i,p_j,\omega) \]

under scenario \(\omega\).

A route enters the decision-ready set only if:

\[ \operatorname{Ready}(r_i) \iff \operatorname{StandingCovered} \land \operatorname{ProtectedConditionsRespected} \land \operatorname{ConsentSatisfied} \land \operatorname{AuthoritySatisfied} \land \operatorname{CapacityAdequate} \]

The decision-ready set is:

\[ R^\star = \{r_i \in R : \operatorname{Ready}(r_i)\} \]

Optimization, MCDA, voting, negotiation, or another decision rule may then operate over \(R^\star\).

The output remains rule-relative:

\[ r^\dagger = \mathcal{D} \left( R^\star, W, \Omega, G \right) \]

where:

  • \(W\) represents weights or ordering rules;
  • \(\Omega\) represents scenarios and uncertainty;
  • \(G\) represents governance constraints.

The framework does not define one universal \(\mathcal{D}\).

That is deliberate.

---

27. Evaluation criteria

A navigation system should be evaluated on more than decision accuracy or participant satisfaction.

27.1 Standing coverage

Were materially affected centers represented?

27.2 Source fidelity

Can each telic item be traced to statement, delegate, observation, or inference?

27.3 Type integrity

Were boundaries, protected conditions, preferences, and uncertainty kept distinct?

27.4 Route diversity

Did the process generate materially different routes rather than variations of one default?

27.5 Cost-bearer visibility

Were externalized costs and future burdens identified?

27.6 Authority legibility

Could participants determine who was entitled to decide or refuse?

27.7 Consent validity

Did authorization match actual recruitment?

27.8 Reversibility

Could the route be staged, corrected, or exited?

27.9 Minority preservation

Did summaries and aggregation preserve protected dissent?

27.10 Robustness

Did the route remain acceptable across plausible scenarios?

27.11 Stop competence

Did the system reduce authority when the field was inadequate?

27.12 Later recognition

Could participants later recognize why the decision was made and what remained unresolved?

---

28. Empirical program

28.1 Navigation versus optimization study

Compare:

  • single-objective optimization;
  • multiobjective optimization;
  • MCDA;
  • polytelometric pre-navigation followed by MCDA.

Measure:

  • objective admission;
  • protected-condition preservation;
  • route diversity;
  • participant recognition;
  • later regret.

28.2 Boundary-versus-weight study

Present the same concern as:

  • a low-weight objective;
  • a constraint;
  • a protected condition.

Measure route selection and participant judgment.

28.3 Cost-bearer study

Compare ordinary tradeoff tables with explicit cost-bearer maps.

Measure externalization recognition and route revision.

28.4 Deliberation study

Compare:

  • preference collection;
  • consensus summary;
  • argument map;
  • polytelometric field map.

Measure minority preservation, correction, route generation, and false consensus.

28.5 Human–AI study

Compare:

  • recommendation-only AI;
  • explainable AI;
  • deliberative AI;
  • non-sovereign navigation assistant.

Measure appropriate reliance, authority confusion, route diversity, and source recognition.

28.6 Robustness study

Compare nominally optimal routes with robust adaptive routes carrying standing and consent constraints.

Measure performance and harm across scenarios.

28.7 Stop-condition study

Test whether explicit missing-standing and authority failures cause appropriate pause rather than forced output.

---

29. Falsification and failure

The framework should be weakened if:

  • it adds no value beyond good problem structuring and MCDA;
  • field classification is unreliable;
  • participants cannot distinguish protected conditions from preferences consistently;
  • the navigation record creates excessive burden;
  • route generation produces irrelevant option inflation;
  • stopping becomes procedural avoidance;
  • source correction does not improve later recognition;
  • models continue to dominate through framing despite non-sovereignty rules;
  • the process privileges articulate participants;
  • protected categories become strategic veto tools;
  • no scalable method can preserve minority fields;
  • the framework delays urgent protective action.

The term polytelometry should be retired if it implies measurement precision that the practice cannot support or if established terms such as value-focused thinking, problem structuring, deliberative decision support, or multi-criteria navigation perform the same work more clearly.

---

30. Ethical boundaries

Polytelometric navigation must not become a requirement that every person disclose their full field before participating.

Minimum necessary projection still governs.

Nor should the method treat all teloi as equally legitimate.

A harmful or coercive purpose can be represented without being protected.

Standing does not mean that every demand receives equal authority.

The framework also must not turn protected conditions into unreviewable personal vetoes over other centers' standing.

Protected status requires:

  • source;
  • scope;
  • authority;
  • affected-center analysis;
  • review path.

The method should preserve atelic life.

Not every route requires a defined destination.

Rest, play, refusal, and ambiguity may be legitimate outcomes.

---

31. Conclusion

Plurality is not a defect to be solved before decision.

It is the field in which decision becomes legitimate or illegitimate.

Multiobjective methods can reveal efficient tradeoffs. MCDA can structure values. Argumentation can expose reasons. Negotiation can produce agreement. Deliberation can transform understanding. Social choice can authorize collective action. Robust planning can preserve performance under uncertainty.

Polytelometric navigation does not replace these methods.

It asks what they are allowed to operate upon.

Which centers entered?

Which purposes were inferred?

Which conditions were protected?

Which costs were externalized?

Which route remained reversible?

Which authority selected the rule?

Which dissent survived the summary?

When did the loop know enough to act—and when did it know enough to stop?

Polytely names the presence of many goals. Polytelometry names the disciplined effort to make their relations, authority, standing, consent, and consequences legible.

The destination matters.

So does who was allowed onto the map.

So does who was asked to pay for the road.

---

References

Arrow, Kenneth J. Social Choice and Individual Values. Wiley, 1951; revised edition, Yale University Press, 1963.

Belton, Valerie, and Theodor J. Stewart. Multiple Criteria Decision Analysis: An Integrated Approach. Springer, 2002.

Dung, Phan Minh. “On the Acceptability of Arguments and Its Fundamental Role in Nonmonotonic Reasoning, Logic Programming and n-Person Games.” Artificial Intelligence 77, no. 2, 1995, 321–357.

Keeney, Ralph L. Value-Focused Thinking: A Path to Creative Decisionmaking. Harvard University Press, 1992.

Lempert, Robert J., Steven W. Popper, and Steven C. Bankes. Shaping the Next One Hundred Years: New Methods for Quantitative, Long-Term Policy Analysis. RAND Corporation, 2003.

Ma, Shuai, et al. “Towards Human-AI Deliberation: Design and Evaluation of LLM-Empowered Deliberative AI for AI-Assisted Decision-Making.” arXiv:2403.16812, 2024.

Osika, Zuzanna, et al. “What Lies beyond the Pareto Front? A Survey on Decision-Support Methods for Multi-Objective Optimization.” arXiv:2311.11288, 2023.

Rittel, Horst W. J., and Melvin M. Webber. “Dilemmas in a General Theory of Planning.” Policy Sciences 4, 1973, 155–169.

Roijers, Diederik M., et al. “A Survey of Multi-Objective Sequential Decision-Making.” Journal of Artificial Intelligence Research 48, 2013, 67–113.

Sen, Amartya. Collective Choice and Social Welfare. Holden-Day, 1970.

Simon, Herbert A. “A Behavioral Model of Rational Choice.” The Quarterly Journal of Economics 69, no. 1, 1955, 99–118.

Small, Christopher T., et al. “Opportunities and Risks of LLMs for Scalable Deliberation with Polis.” arXiv:2306.11932, 2023.

Zhu, Shenzhe, et al. “Can AI Truly Represent Your Voice in Deliberations? A Comprehensive Study of Large-Scale Opinion Aggregation with LLMs.” arXiv:2510.05154, 2025.