Library / Sections / Research

Research

Foundry discovers the evidence universe. SISO Knowledge preserves it. Evidence Engines turn it into traceable claims. Frontier Questions keep the highest-leverage questions and their answer lineage alive.

R—01
01
SISO Knowledgeknowledge_system · active
02
SISO Foundryapplication · active
03
SISO Evidence Enginesbundle · active

God Questions Observatory. 2 answered · 2 partial · 1 researching · 2 scoped across 7 standing questions.

Program substrate. 3 questions · 7 assumptions · 10 evidence connections · 8 action/learning links.

Questions drive the portfolio. Research state is distinct from public answer maturity; artifact-free metadata seed Releases are not accepted answers.

Frontier Questions · God Questions

Questions worth answering again.

7 standing questions with stable identities, explicit evidence scopes, and versioned-answer contracts. Metadata seed Releases are not accepted answers.

GQ-001partial

How should the complete agent workspace be designed across code layout, agent architecture, memory, enforcement, and agent-generated user interfaces?

A standing research question about the complete code, agent, memory, enforcement, and user-interface architecture of an agent-native workspace.

Steward: SISO Open Source Foundation · Lifecycle: active · Freshness: current

Next useful work: Run one cold reconstruction task against the typed workspace boundary and compare errors, intervention, and elapsed time with the prior evidence path.

Public answer: not released

hybrid
GQ-002answered

What changes would make the complete provider-neutral SISO agent layer ten times more effective per unit of time, attention, and compute?

A standing research question about making a provider-neutral multi-agent operating layer materially more effective, efficient, observable, and self-improving.

Steward: SISO Open Source Foundation · Lifecycle: active · Freshness: current

Next useful work: Run one paired agent task with and without the evidence-aware context and receipt path, including retrieval and repair overhead in the comparison.

Public answer: not released

hybrid
GQ-004scoped

For a named software primitive, which implementation is best for the stated context, and is it safe and valuable to reuse, vendor, or learn from?

A parametric standing question for identifying the best implementation of a reusable software primitive across the corpus with quality, rights, and composability evidence.

Steward: SISO Open Source Foundation · Lifecycle: experimental · Freshness: not declared

Next useful work: Define the minimum public-safe question program before scheduling research.

Public answer: not released

corpus
GQ-005scoped

Which categories, techniques, and projects are gaining real momentum, what mechanisms explain the change, and what does the acceleration predict next?

A standing research question about which technologies, categories, techniques, and projects are accelerating and what those changes predict.

Steward: SISO Open Source Foundation · Lifecycle: experimental · Freshness: not declared

Next useful work: Define the minimum public-safe question program before scheduling research.

Public answer: not released

corpus
GQ-006partial

How should the information organ continuously gather, preserve, query, and push valuable evidence into authorized agent workflows and self-improvement loops?

A standing research and systems question about making broad, continuously refreshed evidence reliably accessible to every authorized agent workflow.

Steward: SISO Open Source Foundation · Lifecycle: active · Freshness: not declared

Next useful work: Define the minimum public-safe question program before scheduling research.

Public answer: not released

hybrid
GQ-008answered

Which available model should own each recurring work shape after quality, reliability, tool use, latency, quota, and cost are evaluated together?

A standing research question about which available model should own each work shape after capability, reliability, latency, quota, and cost are considered together.

Steward: SISO Open Source Foundation · Lifecycle: active · Freshness: not declared

Next useful work: Define the minimum public-safe question program before scheduling research.

Public answer: not released

hybrid
GQ-009researching

How should the Great Library make God Questions visible, composable, continuously updated, and connected to evidence, decisions, approved action, and capability learning without becoming the corpus warehouse or execution runtime?

Which registry fields, Library projections, evidence interfaces, and action-return contracts should become the standard infrastructure for every SISO God Question?

Steward: SISO Open Source Foundation · Lifecycle: active · Freshness: current

Next useful work: Measure whether cold readers can reproduce the public estate dispositions without private context, then route one independently adjudicated runtime receipt before expanding the action bridge.

Public answer: not released

hybrid

Research systems

The machinery behind the answers.

3 independently owned Works.

knowledge_systemactive

SISO Knowledge

The durable knowledge-production system for acquiring, curating, storing, indexing, relating, and retrieving SISO knowledge while keeping large or rights-bearing data outside Git.

gls:work:44d2c4da-9998-4d60-b6d1-93465ac25302
applicationactive

SISO Foundry

A source-mining and reuse-knowledge platform for discovering, evaluating, preserving, and navigating valuable external and SISO source.

gls:work:ec664d93-df93-48c5-be40-5d0165886c01
bundleactive

SISO Evidence Engines

A Research package family for source-grounded knowledge items, credibility-ranked engineering principles, and evidence-gated improvement ideas.

gls:work:231aab36-e763-4374-bc94-3a09fd3bf49f