Recommendations, Menus, and Semantic Action Fields

1. A menu is a semantic action field

A menu is not merely a list of buttons and it is not a classifier that reduces the person's meaning to one label. It is a semantic action field: a visible, bounded set of meaningful next movements over which a model can recommend, a person can steer, and deterministic software can resolve an exact consequence.

This turns the workflow architecture into an interaction. The recommendation system does not add a separate semantic brain. It makes the orientation before reasoning and the return to human purpose after reasoning more explicit.

The cycle returns to the person before a new Why begins. Integration curates possibilities from what formed, but ignore, correction, open continuation, exploration, and authorization remain distinct human responses; the menu never closes the free-text route.

The person always retains ordinary free-text input, persistent navigation, and an open path beyond supplied options. A curated menu bounds available effects; it does not bound the conclusions a person or model may consider.

2. Three distinctions that govern the model

Context signals

Multi-valued observations about what is present:

domains: [product, research]
capabilities: [evidence-synthesis, planning]
output_types: [research-program]
subjects: [local-intelligence]
audiences: [deep-tech-researchers]
channels: []
document_refs: [current-thinking-file]
emergent_terms: [semantic-sovereignty]

Signals shape context and retrieval. They do not select an action or force one classification.

Navigation focus

An optional singular category and subcategory organizing the immediate horizon.

A turn can carry several domain signals while using one branch as current navigation.

Action selection and consequence

A distinct person-authorized consequence. A model can recommend an exact supplied workflow, Explore branch, document development, or integration review. It does not execute unless the person chooses it or a prior, bounded grant already covers it. Recommendation and authority remain separate even when the recommendation is excellent.

3. Menus change cognition without code interpreting prose

One thinking route uses compact controls:

DEPTH — Light | Regular | Deep
APERTURE — Focused | Continuity | Telescopic
GROUND — Past | Present | Future
CONDITION — Clear | Uncertain | Tension
GUIDANCE — selected reasoning instructions
SUGGESTED ACTIONS — visible optional next movements

The semantic sequence is:

1. a framing seat reads the current situation and a supplied menu;
2. it returns exact selections;
3. deterministic mechanisms validate and resolve those positions;
4. the reasoning seat receives the resolved natural-language guidance;
5. it does not receive menu mechanics or rejected options.

The model chooses meaning within the supplied field. Code resolves identity, version, and permitted effect. Code does not read free-form text and decide that it “sounds Deep” or “must be Product,” and the model does not invent an executable identity because it sounds appropriate.

4. Orientation / Why (P1)

P1 reads:

• the person's current input and composed ground;
• reasoning controls;
• a complete top-level navigation menu plus Open;
• controlled context-signal options;
• any prior menu whose explicit take-up must be resolved.

It can produce:

• opening read;
• depth, aperture, ground, condition, and guidance selections;
• continuity: continue, shift, or open;
• optional category;
• multi-valued context aperture;
• prior-menu take-up;
• one focus.

P1 does not select a workflow, command, effect, destination, or subcategory action.

5. Substantive movement / How (P2)

P2 receives the resolved orientation and all admitted cross-domain ground.

It produces:

• person-facing reasoning;
• a concise trace describing the movement.

The trace supports continuity. It is not hidden chain of thought and does not outrank the public response or sources.

P2 does not need the workflow carrier horizon or Next Menu. This protects the substantive reasoning from premature action selection.

6. Integration horizon / What (P3)

P3 reads:

• the completed exchange;
• resolved Why context;
• relevant supplied subcategories;
• controlled signal options;
• a snapshot-bound eligible-action horizon;
• top-level categories only for possible context pivots.

It can produce:

• assessment of what formed;
• category fit and optional subcategory;
• next context: continue, broaden, shift, or complete;
• carried-forward and newly introduced signals;
• optional integration orientation;
• zero to four exact next-menu items;
• public bridge.

P3 distinguishes a factual eligible carrier from an expert recommendation and a recommendation from person take-up.

Within the reasoning-turn envelope, P3 contributes to landing, integration, and implication. It does not become a new center of intelligence and does not automatically turn every implication into a next action. It can return an immediate, bounded choice to the person while deeper work already covered by a valid grant continues asynchronously, provided that work remains bound to its origin, return contract, and authority ceiling.

7. Next-menu families

A curated Next Menu can include:

1. Continue thinking — develop a precise focus.
2. Develop document — form a standalone artifact with title and ask.
3. Workflow — select one exact candidate from supplied accepted workflows.
4. Review integration — inspect one exact supplied integration possibility.
5. Change context — reorient the next turn to one exact category without executing work.

Persistent controls remain outside the generated menu:

• change direction;
• keep thinking without choosing an action;
• enter ordinary free text.

The open route is architectural, not decorative. It protects the system from mistaking its present ontology for the complete space of thought.

8. Explore has two related meanings

Explore as a person-facing space

An open environment for a question, idea, or half-formed direction. It should not force a deliverable, deadline, or premature decision.

The system can ask discriminating questions, connect relevant context, and name directions or constraints as they form.

Explore as a bounded delegated inquiry

When a consequential unknown exceeds one turn, an Explore directive defines:

• exact unknown or alternative;
• why the return matters;
• accepted ground and source range;
• inquiry method;
• boundaries and authority;
• evidence-shaped return;
• stop condition.

The inquiry is a loop with a receiving judgment, not a one-way research pipeline. Findings return with evidence, contradiction, and limits; only then can the origin authorize integration, renew the inquiry, or preserve it as a branch with a re-entry condition.

Explore opens knowledge. It does not automatically integrate its own result or execute a proposed action. Its return must re-enter the originating question, file, plan, or decision through an explicit reintegration judgment.

9. Internal menus and visible suggestions differ

Internal menu

Can be technical, broad, explicit about recognition and contraindications, and invisible to the person.

Visible suggestion

Should be plain, sparse, timely, optional, and connected to a meaningful possibility.

Not every internal option should become visible. The system can be capable of offering without constantly producing an offer.

10. Exact eligibility and semantic curation

The host can compile an eligible horizon from exact known relationships:

• person-selected continuation;
• active-work continuation;
• prior-capability continuation;
• exact accepted input;
• authored workflow follow-on;
• exact integration review;
• subcategory entry point;
• category fallback.

The compiler determines eligibility and exact identity. P3 determines contextual usefulness. The person determines consequence. Eligibility can be derived from canonical local files and accepted relationships; generated indexes and menus remain rebuildable views rather than a new canonical authority.

This division reduces hallucinated actions without asking deterministic code to understand the person's meaning.

11. Human authority is a meaningful cognitive act

Authority is not measured by the number of confirmation clicks. A human judgment is meaningful when the person encounters an unresolved choice, has enough evidence to understand the difference, can practically override the recommendation, and can see what consequence follows.

Depending on the movement, the relevant act may be to:

• form an initial view before receiving advice;
• compare two alternatives and their assumptions;
• inspect a source or contradiction;
• diagnose why a result differs from expectation;
• state confidence or acceptance criteria;
• choose which uncertainty may remain unresolved;
• justify why a consequential change should become durable ground.

Low-risk, reversible work should not be interrupted by ritual approval. Consequential work should not be hidden behind a generic “continue” button. The interface should ask for judgment where human purpose, value, accountability, or irreversible consequence actually enters.

The trusted action path

For a consequential operation, the person should approve a display rendered from the canonical target, current version, exact parameters, and computed change—not from the model's narrative about what it intends to do. The approved boundary event must be the one that executes. This protects human authority from becoming approval theater while leaving the semantic recommendation open to explanation and challenge.

12. Prior state changes order, not availability

If prior work focused on one branch, that branch can become more prominent. It cannot erase other categories or Open.

prior context
  → ordering and bearing
    ≠ permanent classification
      ≠ deletion of alternatives

Recommendation state is scoped to the originating file, project, or work context. It should not become a global identity profile.

13. Produced, observed, recommended, selected, authorized, and executed

The two diamonds prevent interest from becoming operational authority. A person may ignore or park the recommendation; even selected work may end with a proposal that changes nothing. Execution begins only after exact authorization, then must be verified and reviewed for reintegration.

These transitions must not collapse. Selection admits a movement; it does not grant epistemic acceptance or unrestricted operational authority. A recommendation can be excellent and remain inert.

14. Empty menus and no recommendation are valid

P3 may return zero next actions when:

• the response itself is sufficient;
• the work has an honest stopping point;
• available actions do not fit;
• uncertainty needs to remain open;
• an offer would interrupt a more important line;
• the person is already clearly directing the next movement.

The quality of the system includes its restraint.

15. Person correction

The person can:

• reject a category;
• select Open;
• ignore a suggestion;
• choose a different workflow;
• continue in natural language;
• clarify a context signal;
• reopen a prior branch;
• state that no further action is wanted.

Correction should update origin-scoped context without rewriting history or turning one correction into a universal preference.

16. Failure modes

Classification capture

One selected category is treated as the complete meaning of a mixed-context turn.

Recommendation execution

A model-generated menu item starts work without person take-up.

Keyword routing

Code interprets free-form text rather than resolving supplied selections.

Menu monopoly

Generated choices become the only way forward.

Engagement optimization

The system surfaces actions to keep activity high rather than because the work earned them.

State globalization

A local navigation focus becomes a persistent profile across unrelated work.

Invented carrier

The model names a workflow, command, or destination not supplied by the current snapshot.

Approval theater

The person is asked to click often but cannot inspect, alter, or reliably bind the consequential action.

Anchoring by menu

The first supplied options narrow attention so strongly that an important unsupplied path is never considered.

17. Research evaluation

Evaluate whether:

1. multi-valued signals preserve mixed-context turns;
2. optional singular focus improves navigation without misclassification;
3. P1 orientation improves substantive P2 reasoning;
4. separating P3 recommendation from P2 reduces action bias;
5. menu selections resolve correctly through exact candidates;
6. people understand recommendation versus execution;
7. Open and free-text routes remain useful;
8. recommendation state stays origin-scoped;
9. empty menus occur at appropriate rates;
10. Explore returns materially change named receiving objects without scope expansion;
11. judgment points improve source use, error detection, or later understanding rather than merely increasing clicks;
12. trusted action displays match the exact operation that executes.

18. Research connection: engagement requires judgment, not generic friction

AIOS proposes menus as a way to make cognitive and operational possibilities visible while preserving an open path. Research on human–AI interaction sharpens what would make that interface substantive. In one tested ideation setting, Wong and Qiu found that a human-first interaction improved later unaided transfer. A CHI study by Kim and colleagues found that source and contradiction cues can help users detect error, while explanations can also make wrong answers more persuasive. The Consent Integrity preprint formalizes a related operational requirement: trusted software should render the actual boundary action and bind approval to what executes.

These findings support initial views, source inspection, comparison, and trusted execution as mechanisms worth building and testing. They do not show that every choice improves cognition, that friction is inherently beneficial, or that human approval makes a decision accurate, ethical, or lawful. Menus can also anchor attention, overload the person, or disguise a predetermined route. The AIOS claim is therefore architectural: meaningful choices and exact effects can occupy the same interface without collapsing into one authority layer.

Read deeper in the cognitive agency brief, its full research memo, the AI-native architecture brief, and its full research memo.

Menus expose the next local movement. Projects and plans preserve why that movement matters across a much longer horizon, while bounded semantic sovereignty governs the transition from recommendation to effect.