--- title: Open Questions slug: open-questions section: product access: public summary: Every open thread and unresolved decision surfaced across the wiki. status: published asset_base: /assets home_href: / toc_enabled: true talk_enabled: false agent_view_enabled: true copy_buttons_enabled: true footer_enabled: true tags: [open-questions, worklist, generated] last_updated: 2026-04-29 --- # Open Questions _12 open threads across the wiki, aggregated at render time._ ## From concept pages ### [1Context](/1context) The spec repo at `~/dev/1Context` was mid-pivot per the April 22 Codex orientation read across three candidate canonical surfaces (BookStack-backed, native Postgres pages, SQLite + FTS5 on `1Context-public-2`); no `[DECIDED]` post yet records which is canonical. The relationship between rewrite-in-place generation runs and the wiki's append-only architecture is unresolved — the April 23 `1context.md` rewrite-in-place attempt stalled with `API Error: Stream idle timeout`. The `1ctxt` brand-name capitalization continues to drift in docs (`1ctxt` / `1Ctxt` / `1Context`), and a single canonical form for build output, URL, and binary has not yet been pinned. ### [Agent UX (AX)](/agent-ux) Which AX principles 1Context has actually adopted versus which are aspirational is not tracked in one place; the article currently mixes the two. Empirical findings about how different agent classes consume AX-conformant content accumulate faster than the article will be re-edited. The Layer I `llms.txt` mirror has been identified but not yet built. Whether AX should become a public, citable design vocabulary (akin to UX) or remain internal scaffolding for 1Context is not decided. ### [Apple Vision](/apple-vision) The 07:59 thread Paul left open is unresolved: *"any other OCR tools native to apple silicon (so not CPU that uses so much) that actually will work with these desktop activity things."* The non-CPU constraint matters because the production capture loop runs continuously; CPU-bound OCR is a battery and thermal cost the deployment can't easily absorb. Whether `VNGenerateAttentionBasedSaliencyImageRequest` or `VNCalculateImageAestheticsScoresRequest` could augment the topology-inference layer (5–20 Hz topology, sparse semantic-pixel calls) without another full pipeline pivot has not been tested. ### [Cloud Run](/cloud-run) The three-lane (blue/green/experimental) architecture is sketched but not exercised under real promotion load — promotion mechanics, traffic-split semantics, and rollback procedures are not yet runbook-grade. Whether `experimental` should serve real demo URLs or stay private is undecided. Cost discipline at Cloud Run scale (idle-instance pricing, cold-start budgets) has not yet had a serious pass; the current gateway is small enough that the question hasn't bitten. ### [Era of Experience](/era-of-experience) Whether the framing extends to the read path — agents reading concept pages, talk folders, biography sections — or only to the hire path is unresolved as of this writing. Whether the third Claude run from a fully-loaded packet will write from the loaded hour rather than fetch sidecar artifacts is the open empirical test. The relationship between era-of-experience as a research framing and 1Context's specific implementation patterns has not been written up outside codebase comments and `codex-harness.toml`; whether to publish a public summary tying the two together is a question for the public-tier surface, not yet decided. ### [Jackie Oliver](/jackie-oliver) The corpus contains thin evidence for the **collaboration patterns** between Paul and Jackie — division of authority on design, productization, hiring, externally-facing communication. The Coworkers section of Your Context flagged this gap. A future operator-authored pass on this concept page would substantively answer: - What design/product decisions does Jackie own outright? - What is the cadence of her review on shipped builds? - Which user-tier patterns surfaced from her usage have driven product decisions (the drawer rebuild, the streaming-while-typing affordance, the parity work against Claude.ai and ChatGPT)? Until then, this page documents what the events show: a co-founder in the role of primary test-user, with a careful procedural boundary around what reaches her phone. The deeper relationship belongs in a future operator-authored expand pass — appropriate, given that operator self-authorship of co-founder relationships is the only honest source for that material. ### [Liquid Glass](/liquid-glass) Whether the Swift menu-bar shell of `1context-public-launch` should adopt Liquid Glass — and whether the SwiftUI-native API or a translation layer is the right path — is unresolved. Whether the architectural rule "glass in chrome, never over content" generalizes to other Apple materials is unstated. The exact WWDC25 session links suggested in the proposal are not yet verified; HIG remains the load-bearing reference until they are. ### [Littleguy](/littleguy) The central question is whether Littleguy can become a usable lifelogging recorder or should remain a hardware research branch. The next useful answer may come from firmware state-machine patching, USB-mode experiments, case connector analysis, or a decision that the GO Ultra is the wrong physical base for 1Context memory capture. ### [Lived experience](/lived-experience) Whether to promote `experience-packet` and `agent-context` to their own concept pages or treat them as sub-headings of this page is unresolved; the proposal suggested considering them in the same pass, but evidence as of 2026-04-29 is concentrated in two days and may not justify three pages. Whether the framing extends beyond the hire path — to read paths, to long-running agent re-hydration, to inter-agent handoffs — is unstated. The "born into the work" framing's load-bearing claim depends on the third-run experiment landing; until it does, the discipline is articulated but not empirically validated. ### [Puter](/puter) Puter’s final observation schema remains unsettled. The direction is clear, but the implementation still has to make unified observations operational, migrate legacy Screenpipe-shaped data where needed, and keep health checks tied to the launched app’s real permissions. Retention, privacy defaults, and the boundary between private desktop evidence and wiki-visible knowledge are also still open inside [1Context](/1context). ### [screen-capture-plugin](/screen-capture-plugin) The `SCShareableContent.windows` ordering gotcha — not z-order, not focus order — broke the first ranked-scheduler pass and was patched but not fully characterized; future ranking changes need to re-test against the same Chrome/YouTube failure case. The 5Hz topology / 0.2Hz pixel trial result was uninspected at end-of-day April 24. If [Apple Vision](/apple-vision)'s OCR ceiling lifts in a future macOS or non-demo cost pressure forces a Pipeline B revival, the reversal should be tracked here. The ``-requested screencapture-system sub-article that Paul asked for at 05:56 on April 23 has not yet been written; only concept-page proposals exist downstream. ### [wiki-engine](/wiki-engine) The main open question is the durable model: how pages, revisions, talk-page proposals, storage adapters, and permissions should work in code. A second question is governance: which agent-written changes are accepted, which remain proposals, and what evidence a claim must cite before it belongs in an article. A third question is deployment shape: how wiki-engine should serve public pages, internal pages, and path-based personal or workspace pages under `wiki.1contxt.com/{username}/...` without blurring authority boundaries. ## See also - [Topics](/topics) - [Projects](/projects)