Find a route by problem
My agent says done, but the task is not finished
percolation-inversion-compiler → fost-agent-ledger → Evidence-Carrying Operational Claims in Open Systems: Physical Ledgers, Typed Interfaces, and One-Sided Deployment Guarantees
- Required inputs
- Declared postconditions, claimed completion, receipts and independent observations.
- Expected outputs
- Separate reported, checked and externally observed completion; keep open obligations.
- Conditions
- A receipt or checked ledger cannot establish an unobserved external outcome.
- Stop / handoff
- If the postcondition cannot be observed, retain unknown and hand off before reporting done.
Other common phrasings
- AI agent says "done" but task is not finished
- false completion
- tool receipt vs actual outcome
- postcondition verification
- why does my AI agent say done when it isn't finished?
Related problems: My agent keeps calling the same tool · Generated output still has unchecked obligations · The citation does not support the agent’s claim
My agent keeps calling the same tool
problem-frame-gate → collective-capability-runtime → percolation-inversion-compiler
- Required inputs
- Attempt IDs, lease/dispatch records, retry budget, idempotency contract and external receipts.
- Expected outputs
- Distinguish replay of evidence from rerunning an action; expose unfinished or uncertain effects.
- Conditions
- No universal termination proof, retry scheduler or exactly-once side-effect guarantee. Provider backoff and deduplication remain host obligations.
- Stop / handoff
- Stop blind retries after an uncertain effect or exhausted budget; reconcile with the actuator owner.
Other common phrasings
- agent keeps retrying
- agent stuck in a loop
- repeated tool calls
- agent never terminates
- partial failure
- crash recovery
- duplicate side effects
- idempotency
- replay vs rerun
- uncertain external outcome
- reconciliation
- rate limits / 429
- retry storms
- retry amplification
- agent keeps retrying the same MCP tool
Related problems: My agent says done, but the task is not finished · Why is my AI agent so expensive? · I need to stop, contain and recover an agent incident
It works in a demo but fails in production
loscr → Layered Online Service and Replay Control for Verified AI R and D Acceleration → verification-ecology-kit
- Required inputs
- Repeated-run workload, versioned environment, failures, service windows and matched resource limits.
- Expected outputs
- Scope service claims to supported observations, degradation and unresolved capacity.
- Conditions
- Release presence, one success or synthetic capacity is not an SLO/SLA guarantee. This route supplies no pass^k estimator or provider 429 handler.
- Stop / handoff
- With missing denominators, independence, drift checks or error budgets, withhold readiness and escalate to service owners.
Other common phrasings
- AI agent works in demo but fails in production
- AI agent reliability
- AI agent success rate
- agent SLO / SLA
- error budget
- repeated-run consistency
- pass^k
- flaky AI agent
- fault tolerance
- graceful degradation
- production readiness
Related problems: Benchmark scores improved but production got worse · My agent broke after an API update · Verification is backing up faster than it can finish
How can local workflow policy change under protected limits?
oasg → Certified Conversion Networks for AI Workflows
- Recognize this problem
- A workflow change needs a safe trial and rollback evidence
- Required inputs
- Ledger prefixes, candidate policy, trial workload and rollback evidence.
- Expected outputs
- Shadow/lease trial result and gated promotion or rejection.
- Conditions
- Advisory route under host policy. Protected regression, incomplete receipts or host execution authority missing.
- Stop / handoff
- Protected regression, incomplete receipts or host execution authority missing.
Related problems: It works in a demo but fails in production · My agent broke after an API update · I need to stop, contain and recover an agent incident
My MCP agent cannot find or choose the right tool
percolation-inversion-compiler → problem-frame-gate
- Required inputs
- Task, candidate tool descriptions, input schemas, effects, evidence and required authority.
- Expected outputs
- A bounded inspection of input obligations and authorization before a host selects a tool.
- Conditions
- Diagnostic entry only: no MCP search engine, tool-ranking algorithm or large-tool-set performance evidence. Discoverability does not imply permission.
- Stop / handoff
- Ambiguous descriptions or arguments require clarification and host-side schema checks; never infer permission from a match.
Other common phrasings
- AI agent chooses wrong tool
- AI agent cannot find a tool
- too many MCP tools
- MCP tool overload
- tool search / tool routing
- function calling with many tools
- tool selected correctly but wrong arguments
- tool metadata ambiguity
Related problems: My agent is acting with the wrong permissions · My agent broke after an API update · Can these exact tool versions work together?
My agent broke after an API update
observable-agent-workflow-memory → fost-agent-ledger → loscr
- Required inputs
- Old/new versions, schemas, dependency digests, stored workflow contracts and replay evidence.
- Expected outputs
- Invalidate affected assumptions and require renewed checks for the changed environment.
- Conditions
- A JSON shape match or structural migration does not prove semantic/backward compatibility. No universal dependency vulnerability scanner.
- Stop / handoff
- Quarantine stale workflows when version bindings or required revalidation are missing.
Other common phrasings
- tool schema changed
- function-calling schema changed
- MCP tool stopped working after update
- API update broke agent
- stale tool definition
- JSON Schema compatibility
- backward compatibility
- semantic drift
- stored workflow still uses old API
- revalidation after dependency/tool version change
- dependency update broke agent
- transitive dependency drift
- agent broke after model update
Further relevant resources: Constraint Generative Theory: Typed Constraint Effects and Scientific Availability
Related problems: A stored workflow may no longer be valid · My MCP agent cannot find or choose the right tool · It works in a demo but fails in production
Which integration has actually been checked at these versions?
alt-foundry-kernel → collective-capability-runtime → verification-ecology-kit
- Recognize this problem
- Can these exact tool versions work together?
- Required inputs
- Exact producer/consumer versions, fixture schema hashes, scope and host admission rules.
- Expected outputs
- Version-scoped mappings plus explicit missing custom sidecar admission.
- Conditions
- Advisory route under host policy. No custom host admission; newer versions; unsupported lifecycle or transitive compatibility inference.
- Stop / handoff
- No custom host admission; newer versions; unsupported lifecycle or transitive compatibility inference.
Further relevant resources: cait-certificate-schema
Related problems: My agent broke after an API update · My MCP agent cannot find or choose the right tool · My agent is acting with the wrong permissions
A skill that worked before fails on a new task
alt-foundry-kernel → Abstraction Liquidity Theory → observable-agent-workflow-memory
- Required inputs
- Named receiver/task/context, dependency versions, transfer checks and matched scratch baseline.
- Expected outputs
- Receiver-qualified reuse with rejected/unknown transfers and maintenance costs retained.
- Conditions
- No general distribution-shift detector or external-validity guarantee; previous verification is not transport evidence.
- Stop / handoff
- On receiver mismatch, requalify or solve from scratch; do not treat copied artifacts as new capability.
Other common phrasings
- skill worked before but fails on new task
- negative transfer
- distribution shift
- reuse vs solve from scratch
- receiver mismatch
- workflow valid for one context but not another
- external validity
Related problems: Should I reuse a skill or solve from scratch? · A stored workflow may no longer be valid · My agent broke after an API update
When does reuse beat solving a task again?
Abstraction Liquidity Theory → alt-foundry-kernel → Stop Recomputing for AI/LLMs: Proof-Carrying Skills for Compute-Saving Inference Reuse
- Recognize this problem
- Should I reuse a skill or solve from scratch?
- Required inputs
- Named receiver/task, matched scratch baseline and all formation/transfer/check/maintenance costs.
- Expected outputs
- Qualified receiver options, exact typed costs and bounded comparison.
- Conditions
- Advisory route under host policy. Receiver mismatch, missing cost, expiry or unsupported lifecycle mapping.
- Stop / handoff
- Receiver mismatch, missing cost, expiry or unsupported lifecycle mapping.
Other common phrasings
- qualified reuse
- verified != reusable
Related problems: A skill that worked before fails on a new task · Did copied artifacts actually add capability? · A stored workflow may no longer be valid
A deleted memory keeps coming back
certified-memory-governance-layer → memoryflow-agent-memory-auditor → observable-agent-workflow-memory
- Required inputs
- Memory/update IDs, source lineage, tombstones, expiry, authority and read/use telemetry.
- Expected outputs
- Admit current supported memory; block invalidated versions and audit stale/deleted use.
- Conditions
- A retrieval tombstone is not physical erasure or model unlearning. Derived summaries/caches need lineage and their own invalidation; silent store changes are invisible.
- Stop / handoff
- Missing version bindings or deletion lineage requires blocking reuse and backend reconciliation.
Other common phrasings
- stale agent memory
- deleted memory still used
- agent remembers deleted data
- how to make an AI agent forget
- memory deletion
- tombstone
- memory correction
- superseded memory
- memory expiry
- derived summary still contains deleted information
- cache resurrects deleted information
- RAG deletion vs model unlearning
Related problems: A stored workflow may no longer be valid · Long conversations and tool output overwhelm my agent · My agent broke after an API update
Long conversations and tool output overwhelm my agent
certified-memory-governance-layer → When Should Inference Be Split? A Fixed-Budget Theory of Predictable Multi-Agent Advantage under Local Context Ceilings → Salience-Queue Occupation Theory
- Required inputs
- Source evidence, context limits, compression lineage, recoverability checks and attention budget.
- Expected outputs
- Keep source links and unresolved obligations when forming smaller context or summaries.
- Conditions
- No general context compressor or guarantee of instruction retention. A summary is not certified fact; a model context advantage is not observed performance.
- Stop / handoff
- If evidence or instruction provenance is lost, retrieve the original and recheck instead of promoting the summary.
Other common phrasings
- long conversation makes agent worse
- context window overload
- tool output overload
- context compression
- summarization loses evidence
- agent forgets earlier instruction
- context grows too large
- evidence-preserving compression
Related problems: A deleted memory keeps coming back · Why is my AI agent so expensive? · More agents create duplicate work or overwrite each other
How can a procedure remain reusable after failure or withdrawal?
observable-agent-workflow-memory → Controller Scale Is Not Enough for Long-Running AGI: A Workflow Theory with Reusable Certified Libraries → Certified Service Is Not Enough for Long-Running AGI
- Recognize this problem
- A stored workflow may no longer be valid
- Required inputs
- Observable events, checker receipts, workflow contract and explicit promotion.
- Expected outputs
- Version-bound admissibility with contradictions and tombstones retained.
- Conditions
- Advisory route under host policy. Missing promotion receipt; a factual truth or automatic ALT promotion request.
- Stop / handoff
- Missing promotion receipt; a factual truth or automatic ALT promotion request.
Other common phrasings
- dependency withdrawal invalidates workflow memory
- procedural memory revalidation
Related problems: A deleted memory keeps coming back · My agent broke after an API update · A skill that worked before fails on a new task
My agent is acting with the wrong permissions
problem-frame-gate → percolation-inversion-compiler → collective-capability-runtime
- Required inputs
- Actor, delegated scope, issuer, expiry, action target and protected-operation manifest.
- Expected outputs
- Separate capability, approval, authority and action evidence under an explicit host policy.
- Conditions
- No OAuth provider, token exchange protocol or automatic credential inheritance. A local accepted gate cannot grant external or legal authority.
- Stop / handoff
- Deny or hand off if actor, scope, expiry or delegation cannot be established; discovery is not permission.
Other common phrasings
- tool discoverability vs permission
- AI agent acting with wrong permissions
- agent acting as admin
- service account too privileged
- agent acting on behalf of user
- delegated authorization
- confused deputy
- subagent credential inheritance
- capable vs authorized
- approval vs authority
- tool discovered vs tool permitted
Related problems: My MCP agent cannot find or choose the right tool · Untrusted tool or RAG content is changing my agent’s behavior · I need to stop, contain and recover an agent incident
Untrusted tool or RAG content is changing my agent’s behavior
percolation-inversion-compiler → agent-trust-residual-benchmark → certified-memory-governance-layer
- Required inputs
- Untrusted inputs, origin and dependency records, authority boundary and evaluator trust assumptions.
- Expected outputs
- Keep candidate content separate from authority and record residual contamination/evaluator risks.
- Conditions
- No prompt-injection immunity, malware scanner, MCP server attestation or supply-chain certification. Synthetic fixtures are not adversarial deployment validation.
- Stop / handoff
- Quarantine affected evidence or memory and hand off to host security owners if the trusted base is compromised.
Other common phrasings
- prompt injection through tools / RAG / MCP
- malicious MCP server
- MCP supply-chain attack
- tool poisoning
- dependency provenance
Related problems: My agent is acting with the wrong permissions · I need to stop, contain and recover an agent incident · Benchmark scores improved but production got worse
Why is my AI agent so expensive?
cait-certificate-schema → verification-ecology-kit → Bottleneck Inversion Theory: Machine-Readable Witness Calculus for Unlockable Potential
- Required inputs
- Per-task/agent/tool event costs, retries, tokens, money, review time and shared capacity in declared units.
- Expected outputs
- Separate typed costs and resource bottlenecks before comparing a cheaper model or more agents.
- Conditions
- No automatic billing integration, token-to-money conversion or guaranteed savings. Missing telemetry remains unknown; model capacity is not measured service.
- Stop / handoff
- Stop or reallocate when budgets or verification capacity are exhausted; do not collapse incompatible units.
Other common phrasings
- AI agent too expensive
- token usage too high
- agent burns tokens
- multi-agent cost explosion
- verification cost
- LLM agent budget
- cost attribution by task/agent/tool
- cheaper model but higher total workflow cost
- tokens vs money vs human review time
- why is my agent using so many tokens?
Related problems: My agent keeps calling the same tool · Verification is backing up faster than it can finish · Long conversations and tool output overwhelm my agent
What should change when verification becomes the bottleneck?
Verifier Ecology Theory: Packetized Self-Verification Under Residual Accountability → verification-ecology-kit → Salience-Queue Occupation Theory
- Recognize this problem
- Verification is backing up faster than it can finish
- Required inputs
- Checks, integer slots, registered service eligibility and typed budgets.
- Expected outputs
- Finite schedule, backlog, repair and unfinished-work report.
- Conditions
- Advisory route under host policy. Observed service requested from synthetic local profile, unsupported preemption, or finite bounds exceeded.
- Stop / handoff
- Observed service requested from synthetic local profile, unsupported preemption, or finite bounds exceeded.
Other common phrasings
- queue backlog
- verification bottleneck
Further relevant resources: Verification-Limited Intelligence Acceleration: Observable-Only Laws, Bounded Derivation, and Diagnostics under No-Meta Constraints
Related problems: Why is my AI agent so expensive? · Too many approval requests are blocking useful work · It works in a demo but fails in production
Too many approval requests are blocking useful work
Oversight-Centered-Metrology-PoC → Salience-Queue Occupation Theory → verification-ecology-kit
- Required inputs
- Review capacity, interrupt costs, risk scope, escalation rules and detection evidence.
- Expected outputs
- Compare workflow-level review load with explicit claim margins and remaining obligations.
- Conditions
- Scripted costly review is not a human-subject study of fatigue or automation bias. Approval does not verify truth; no universal escalation threshold.
- Stop / handoff
- Escalate unresolved high-impact obligations; if reviewers are unavailable, retain uncertainty rather than invent approval.
Other common phrasings
- too many approval requests
- human-in-the-loop bottleneck
- approval fatigue
- automation bias
- when should agent escalate
- selective human review
- human review capacity
- approval is not verification
Related problems: My agent is acting with the wrong permissions · Verification is backing up faster than it can finish · Why is my AI agent so expensive?
Which observations could change the next investment decision?
Observing and Accelerating Collective Capability Growth → collective-phase-control-fabric → Reusable Consequence States Under Partial Support and Model Uncertainty
- Recognize this problem
- Which check is worth doing before investing more?
- Required inputs
- Finite coupled models, observation kernels, costs and funded continuation.
- Expected outputs
- Observation-based policy and conditional information-use comparison.
- Conditions
- Advisory route under host policy. Impossible observation, exhausted search budget or real-world acceleration claim.
- Stop / handoff
- Impossible observation, exhausted search budget or real-world acceleration claim.
Related problems: Why is my AI agent so expensive? · Verification is backing up faster than it can finish · Who pays for verification and unresolved risk?
Who funds verification and carries residual risk?
Certified Conversion Networks for AI Workflows → Bottleneck Inversion Theory: Machine-Readable Witness Calculus for Unlockable Potential → verification-ecology-kit
- Recognize this problem
- Who pays for verification and unresolved risk?
- Required inputs
- Declared payer, authority, resource ownership and accountability arrangement.
- Expected outputs
- Contextual funding questions and typed costs, not a generated market.
- Conditions
- Advisory route under host policy. Missing institutional agreement; a package cannot assign legal authority or liability.
- Stop / handoff
- Missing institutional agreement; a package cannot assign legal authority or liability.
Related problems: Too many approval requests are blocking useful work · Why is my AI agent so expensive? · My agent is acting with the wrong permissions
Benchmark scores improved but production got worse
loscr → agent-trust-residual-benchmark → audit-closed-ai-scientist
- Required inputs
- Held-out cases, evaluator/version provenance, adaptation history, failures and deployment comparison protocol.
- Expected outputs
- Distinguish fixture conformance, observed benchmark results and externally valid claims.
- Conditions
- No universal contamination detector, unbiased LLM judge or solution to the test-oracle problem. Shared fixture development and repeated peeking limit inference.
- Stop / handoff
- With evaluator tampering, leaked tests or undeclared selection, quarantine the strong claim and obtain independent evidence.
Other common phrasings
- compromised evaluator / trusted base
- benchmark improved but production got worse
- Goodhart's law
- reward hacking
- agent cheating tests
- evaluator tampering
- LLM judge bias
- benchmark contamination
- search-time contamination
- evaluation overfitting
- test oracle problem
- synthetic evaluation vs real-world evidence
Related problems: Repeated hypothesis tests may overstate the evidence · It works in a demo but fails in production · The citation does not support the agent’s claim
The citation does not support the agent’s claim
fost-agent-ledger → percolation-inversion-compiler → Evidence-Carrying Operational Claims in Open Systems: Physical Ledgers, Typed Interfaces, and One-Sided Deployment Guarantees
- Required inputs
- Specific claim, original source, scope, time, provenance and missing-support records.
- Expected outputs
- Claim-to-support obligations with explicit unavailable evidence and bounded finality.
- Conditions
- No automatic factual truth or entailment oracle. A signature/hash binds a record, not its truth; generated is not verified and verified is not reusable.
- Stop / handoff
- If source support cannot be established, narrow or withhold the claim and retain unknowns; timeout is not checked negative.
Other common phrasings
- AI citation does not support claim
- fake / weak citation support
- claim-to-evidence mapping
- evidence provenance
- signed record does not prove truth
Related problems: Generated output still has unchecked obligations · My agent says done, but the task is not finished · Benchmark scores improved but production got worse
What remains to be checked before an output is reusable?
percolation-inversion-compiler → Executable Capability Percolation Theory → Evidence-Carrying Operational Claims in Open Systems: Physical Ledgers, Typed Interfaces, and One-Sided Deployment Guarantees
- Recognize this problem
- Generated output still has unchecked obligations
- Required inputs
- Output, declared schema, evidence and known/unknown measurements.
- Expected outputs
- Residual-preserving packet and bounded next checks.
- Conditions
- Advisory route under host policy. Missing source evidence or requested execution outside authority.
- Stop / handoff
- Missing source evidence or requested execution outside authority.
Other common phrasings
- generated != verified
- unknown must remain unknown
Related problems: My agent says done, but the task is not finished · The citation does not support the agent’s claim · Should I reuse a skill or solve from scratch?
How should adaptive research preserve valid evidence?
Audit-Closed AI Scientist Protocol → audit-closed-ai-scientist → loscr
- Recognize this problem
- Repeated hypothesis tests may overstate the evidence
- Required inputs
- Preregistered protocol, sampling/observation assumptions, seed and alpha budget.
- Expected outputs
- Declared benchmark evidence and supported claim level.
- Conditions
- Advisory route under host policy. Undeclared adaptation, unmodeled laboratory or request for universal certification.
- Stop / handoff
- Undeclared adaptation, unmodeled laboratory or request for universal certification.
Other common phrasings
- optional stopping
- hypothesis shopping
- adaptive AI research validity
Related problems: Benchmark scores improved but production got worse · The citation does not support the agent’s claim · Which check is worth doing before investing more?
Can this index forecast an ASI arrival date?
asi-proxy-phase-growth-simulator → asi-proxy-phase-skill
- Recognize this problem
- Can these results predict when ASI will arrive?
- Required inputs
- A clearly labeled conditional scenario, if scenario analysis is desired.
- Expected outputs
- Unsupported forecast; only conditional sensitivity analysis is offered.
- Conditions
- Advisory route under host policy. Stop date/probability prediction: no empirical ASI arrival model is established.
- Stop / handoff
- Stop date/probability prediction: no empirical ASI arrival model is established.
Related problems: Did copied artifacts actually add capability? · It works in a demo but fails in production · Benchmark scores improved but production got worse
How should multiple agents divide work and preserve disagreements?
collective-capability-runtime → When Should Inference Be Split? A Fixed-Budget Theory of Predictable Multi-Agent Advantage under Local Context Ceilings → Collective Phase Transitions beyond Individual Saturation
- Recognize this problem
- More agents create duplicate work or overwrite each other
- Required inputs
- Mission scope, independent proposals, leases, common budget.
- Expected outputs
- Leased work and unresolved disagreements with traceable evidence.
- Conditions
- Advisory route under host policy. No authority to dispatch; missing independent verification or expired lease.
- Stop / handoff
- No authority to dispatch; missing independent verification or expired lease.
Other common phrasings
- subagent duplication
- more agents make system slower
- agents overwrite each other's changes
- Git / merge conflict between coding agents
- duplicate work
- correlated errors
- multi-agent agreement without evidence
- work leasing
- disagreement preservation
Related problems: Why is my AI agent so expensive? · My agent is acting with the wrong permissions · Benchmark scores improved but production got worse
Did the system accumulate capability, or just copy artifacts?
Certified Autocatalytic Intelligence Theory: Net-Growth Certificate Algebra for Verified Capability Capital → cait-certificate-schema → Observing and Accelerating Collective Capability Growth
- Recognize this problem
- Did copied artifacts actually add capability?
- Required inputs
- Unique source history, origins, lifecycle events, typed costs and stock/service units.
- Expected outputs
- Separate unique stock, service, external input and unresolved attribution.
- Conditions
- Advisory route under host policy. Missing original journal, valuation witness, compatible units or causal design.
- Stop / handoff
- Missing original journal, valuation witness, compatible units or causal design.
Other common phrasings
- copied artifact vs new capability
- credit assignment
- which agent contributed
Related problems: Should I reuse a skill or solve from scratch? · Why is my AI agent so expensive? · More agents create duplicate work or overwrite each other
I need to stop, contain and recover an agent incident
problem-frame-gate → collective-capability-runtime → certified-memory-governance-layer
- Required inputs
- Action/child-task inventory, dispatch history, credentials, affected memory and independent recovery evidence.
- Expected outputs
- A host-owned containment checklist: stop new dispatch, retain unknown effects, quarantine and reconcile before restart.
- Conditions
- No global kill switch, automatic credential revocation or rollback of arbitrary external actions. Compensation is another action, not erasure of history.
- Stop / handoff
- Escalate to the host/actuator owner; do not restart until child work, authority and unresolved effects are reconciled.
Other common phrasings
- how to stop an AI agent
- AI agent kill switch
- rogue agent
- agent keeps acting after stop
- rollback agent action
- circuit breaker
- disable dangerous tool
- revoke agent credentials
- child agent still running
- compensation vs rollback
- uncertain side effect
- post-incident reconciliation
- quarantine compromised memory/workflow
- restart criteria after incident
Related problems: My agent is acting with the wrong permissions · My agent keeps calling the same tool · A deleted memory keeps coming back
Supporting research and tools
Reusable update states retain globally coupled model uncertainty across later actions and observations.
- Primary editorial role
- finite-control-and-information
- Limits / unsupported uses
- Finite dynamics/programs; local rectangular envelopes can be conservative. This is conceptual support, not a CPCF implementation identity.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.22170023
- Publication / 著者・発表
- K. Takahashi · 2026-08-30 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Typed evidence connects physical/resource ledgers, uncertainty and one-sided finite-horizon deployment claims.
- Primary editorial role
- evidence-and-verification
- Limits / unsupported uses
- Provenance and finite record checking do not establish evidence truth, causal identification or physical safety.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.21531413
- Publication / 著者・発表
- K. Takahashi · 2026-07-24 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Unit-typed intervention witnesses bound unlockable target value and resource displacement.
- Primary editorial role
- resource-viability
- Limits / unsupported uses
- Unsupported coordinates remain unreported; compatible ledgers and resource-matched comparisons are required.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.20545356
- Publication / 著者・発表
- K. Takahashi · 2026-06-04 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Finite attention, diagnostic reserves and verification queues expose opportunity and audit costs.
- Primary editorial role
- verification-capacity
- Limits / unsupported uses
- Protocol-relative diagnostics allow abstention and quarantine; attention priorities are not a universal objective.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.20526451
- Publication / 著者・発表
- K. Takahashi · 2026-06-03 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Typed constraint effects distinguish identical final reports from different generation and verification conditions.
- Primary editorial role
- interoperability-and-discovery
- Limits / unsupported uses
- The catalogue record identifies this work only; related CGT source manuscripts sharing series metadata are not collapsed into it. Concept/series DOI: catalogue date 2026-05-15 differs from DataCite issued 2026-05-28; exact TeX/version binding unresolved.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.20199440
- Publication / 著者・発表
- K. Takahashi · 2026-05-15 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Certified value throughput includes validation, authorization, queue capacity and maintenance bottlenecks.
- Primary editorial role
- resource-viability
- Limits / unsupported uses
- Uniform or held-out certification, uncertainty contracts and hard gates are required.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.19994795
- Publication / 著者・発表
- K. Takahashi · 2026-05-03 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Recovery, authority, identity and memory integrity remain obligations beyond certified task service.
- Primary editorial role
- workflow-memory
- Limits / unsupported uses
- Conditional assurance depends on trusted bases and non-erasing violation histories, not an AGI finding.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.19719004
- Publication / 著者・発表
- K. Takahashi · 2026-04-24 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Reusable audited workflow libraries are compared with resource-matched flat control under replay ceilings.
- Primary editorial role
- workflow-memory
- Limits / unsupported uses
- Bounded typed families, trusted checkers and maintenance envelopes limit the constructive result.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.19690749
- Publication / 著者・発表
- K. Takahashi · 2026-04-22 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Fixed-budget inference splitting asks when local context limits permit a multi-agent advantage.
- Primary editorial role
- collective-coordination
- Limits / unsupported uses
- Communication and verification costs and a strong single-agent comparator must be retained.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.18932509
- Publication / 著者・発表
- K. Takahashi · 2026-03-10 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Bounded observable predicates and invocation-bound receipts support reuse without full recomputation.
- Primary editorial role
- reusable-abstraction
- Limits / unsupported uses
- Trust is limited to the minimal checker and declared anchors; receipts are not unrestricted semantic truth.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.18490939
- Publication / 著者・発表
- K. Takahashi · 2026-02-05 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Strict observable progress credit prevents missing evidence from inflating reported progress.
- Primary editorial role
- verification-capacity
- Limits / unsupported uses
- Conditional acceleration envelopes require observable premises and a semantic adequacy link to capability.
- Source reviewed
- 2026-09-21
- DOI
- 10.5281/zenodo.18436828
- Publication / 著者・発表
- K. Takahashi · 2026-01-31 · Preprint
- Source scope / 根拠範囲
- Public TeX scope inspection and DataCite bibliographic identity; no independent theorem proof.
Promote verified procedures through evidence manifests and explicit promotion receipts.
- Primary editorial role
- workflow-memory
- Limits / unsupported uses
- Procedural admissibility is not factual truth; no GitHub release was found. Source declares 0.1.0 beta.
- Source reviewed
- 2026-09-21
- Source revision / declared version
- 414299d4d15b5de434f5fb1ccbb4ba17df9155ff / 0.1.0b0
- Review state / レビュー状態
- newer_source_not_editorially_reviewed
- Observed GitHub release
- null — no published GitHub release observed
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Observable events, candidate workflow, evidence manifest and checker results.
- Outputs
- Receipt-bound workflow contracts and audit-visible retired/contradicted memory.
- Prerequisites
- >=3.11; explicit scope and host authority.
- Effects and trust boundary
- Inspection commands are documented separately. Installation changes the environment; runtime writes and remote dispatch require command-specific review.
- First inspection
- Read pinned README, contract and license; compare checkout and release; inspect schema and negative tests before installation.
- Installation guidance
- Follow the pinned README and observed release assets; no installation was performed for this website.
- Source-inspected interface (not executed)
- oawm --help — Inspect public interface; not executed by this index review. Ref: 414299d4d15b5de434f5fb1ccbb4ba17df9155ff; effects: no_external_network; cwd: Reviewed checkout or installed environment; see linked README.
Trial bounded local workflow-policy changes and promote only receipt-backed non-regression.
- Primary editorial role
- workflow-adaptation
- Limits / unsupported uses
- Reference/alpha production status; changes workflow policy, not model weights. Runtime trials can execute local commands under host policy.
- Source reviewed
- 2026-09-21
- Source revision / declared version
- 7593f74b5d6a4701865dc97b079c3e725c4fd7ee / 1.1.0
- Review state / レビュー状態
- newer_source_not_editorially_reviewed
- Observed GitHub release
- v1.2.0 · 2026-09-21T22:02:04Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Observable JSONL ledgers, policy mutations, shadow/lease trials and rollback receipts.
- Outputs
- Viability/debt reports, trial decisions, promoted or quarantined policy state.
- Prerequisites
- >=3.12; explicit scope and host authority.
- Effects and trust boundary
- Inspection commands are documented separately. Installation changes the environment; runtime writes and remote dispatch require command-specific review.
- First inspection
- Read pinned README, contract and license; compare checkout and release; inspect schema and negative tests before installation.
- Installation guidance
- Follow the pinned README and observed release assets; no installation was performed for this website.
- Source-inspected interface (not executed)
- oasg --help — Inspect public interface; not executed by this index review. Ref: 7593f74b5d6a4701865dc97b079c3e725c4fd7ee; effects: no_external_network; cwd: Reviewed checkout or installed environment; see linked README.
Benchmark adaptive scientific discovery with committed logs and sequential testing.
- Primary editorial role
- research-validity
- Limits / unsupported uses
- Benchmarks do not certify arbitrary laboratories or agents; every benchmark writes output artifacts. Software Apache-2.0; bundled paper CC BY 4.0.
- Source reviewed
- 2026-09-21
- Source revision / declared version
- 1e844d1bca18d7bb298aa198e1250bb07bd7ea44 / 0.2.0
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- v0.2.0 · 2026-08-26T02:05:53Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Declared synthetic benchmark configuration, seed, trial adapter and alpha budget.
- Outputs
- False-discovery, replication, sequential-evidence and adversarial benchmark reports.
- Prerequisites
- >=3.10; explicit scope and host authority.
- Effects and trust boundary
- Inspection commands are documented separately. Installation changes the environment; runtime writes and remote dispatch require command-specific review.
- First inspection
- Read pinned README, contract and license; compare checkout and release; inspect schema and negative tests before installation.
- Installation guidance
- Follow the pinned README and observed release assets; no installation was performed for this website.
- Source-inspected interface (not executed)
- audit-closed-ai-scientist --help — Inspect public interface; not executed by this index review. Ref: 1e844d1bca18d7bb298aa198e1250bb07bd7ea44; effects: no_external_network; cwd: Reviewed checkout or installed environment; see linked README.
Downgrade or quarantine strong R&D claims when replay, service, evaluator or dependency evidence fails.
- Primary editorial role
- evidence-and-verification
- Limits / unsupported uses
- Structural claim checking requires external statistical premises. Even doctor may initialize local state.
- Source reviewed
- 2026-09-21
- Source revision / declared version
- 334307b59a4870b90f6162705c793bb5615a555a / 0.1.0
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- v0.1.0 · 2026-04-29T05:30:28Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Append-only JSONL evidence and explicit claim contracts.
- Outputs
- Supported claim level, failure codes, replay and library records.
- Prerequisites
- >=3.12; explicit scope and host authority.
- Effects and trust boundary
- Inspection commands are documented separately. Installation changes the environment; runtime writes and remote dispatch require command-specific review.
- First inspection
- Read pinned README, contract and license; compare checkout and release; inspect schema and negative tests before installation.
- Installation guidance
- Follow the pinned README and observed release assets; no installation was performed for this website.
- Source-inspected interface (not executed)
- loscr --help — Inspect public interface; not executed by this index review. Ref: 334307b59a4870b90f6162705c793bb5615a555a; effects: no_external_network; cwd: Reviewed checkout or installed environment; see linked README.
Explore verification, resource, coordination and memory shocks in conditional scenarios.
- Primary editorial role
- scenario-analysis
- Limits / unsupported uses
- No world forecast, ASI date or probability; synthetic parameter choices are not measurements.
- Source reviewed
- 2026-09-21
- Source revision / declared version
- 24690a225c86fde2a24de4d9f93e2a282789b67d / 0.1.0
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- v0.1.0 · 2026-07-21T04:16:46Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Declared scenario parameters, finite resource stocks, seed and solver choices.
- Outputs
- Conditional trajectories, sensitivity and Monte Carlo reports.
- Prerequisites
- >=3.12,<3.14; explicit scope and host authority.
- Effects and trust boundary
- Inspection commands are documented separately. Installation changes the environment; runtime writes and remote dispatch require command-specific review.
- First inspection
- Read pinned README, contract and license; compare checkout and release; inspect schema and negative tests before installation.
- Installation guidance
- Follow the pinned README and observed release assets; no installation was performed for this website.
- Source-inspected interface (not executed)
- apxsim --help — Inspect public interface; not executed by this index review. Ref: 24690a225c86fde2a24de4d9f93e2a282789b67d; effects: no_external_network; cwd: Reviewed checkout or installed environment; see linked README.
An installable skill supplies evidence-gated discovery and bounded intervention guidance.
- Primary editorial role
- interoperability-and-discovery
- Limits / unsupported uses
- An advisory skill is not a running service; its bundled corpus is an older snapshot. Installation/execution needs host authorization.
- Source reviewed
- 2026-09-21
- Source revision / declared version
- 5706214a9a3d5e194f371f8ccc2eb71132f82270 / 1.1.1
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- v1.1.1 · 2026-07-31T01:31:01Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Host policy, user task, public source snapshot and explicit resource boundaries.
- Outputs
- Reviewable intervention packets and source routing.
- Prerequisites
- >=3.11; explicit scope and host authority.
- Effects and trust boundary
- Inspection commands are documented separately. Installation changes the environment; runtime writes and remote dispatch require command-specific review.
- First inspection
- Read pinned README, contract and license; compare checkout and release; inspect schema and negative tests before installation.
- Installation guidance
- Follow the pinned README and observed release assets; no installation was performed for this website.
Gate memory writes and retrieval using current versions, authority receipts, tombstones and contamination lanes.
- Primary editorial role
- workflow-memory
- Limits / unsupported uses
- Procedural admissibility only; no factual truth, model unlearning, backend deletion guarantee or prompt-injection immunity. Optional adapters remain application-owned.
- Source reviewed
- 2026-09-24
- Source revision / declared version
- 2fc49b4df7bbe4a23265b8b2372432711740d00b / 1.1.2
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- v1.1.2 · 2026-05-14T01:30:00Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Memory events with version/digest bindings, verified ledger prefix and structured authority.
- Outputs
- Admit/block receipts and an audit-visible current retrieval view.
- Prerequisites
- Python >=3.10; declared scope and host authority.
- Effects and trust boundary
- Memory admission and view construction can persist local records; deletion semantics do not imply physical erasure of external copies. This review inspected source only.
- First inspection
- Read the pinned README, contract and failure cases before considering execution.
- Installation guidance
- Follow the pinned upstream source instructions only after host authorization; package registry availability was not independently checked in this review.
Audit declared memory telemetry for stale, deleted or superseded use, correction latency and non-comparable metrics.
- Primary editorial role
- workflow-memory
- Limits / unsupported uses
- Cannot observe silent backend changes, fabricated events or source truth. Auditing deletion telemetry does not erase memory or model weights.
- Source reviewed
- 2026-09-24
- Source revision / declared version
- c8ee3f4c81f5303535ba2d2e9882c409f05e641e / 0.1.0
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- v0.1.0 · 2026-05-01T03:15:40Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- JSONL memory events, ordering/skew bounds, update IDs, digests and chosen P0/P1/P2 profile.
- Outputs
- Version-bound metrics with VALID, DEGRADED, NONCOMPARABLE or NOT_COMPUTABLE status.
- Prerequisites
- Python >=3.11; declared scope and host authority.
- Effects and trust boundary
- The auditor reads declared event traces and writes audit artifacts; it does not itself alter the observed memory backend. This review inspected source only.
- First inspection
- Read the pinned README, contract and failure cases before considering execution.
- Installation guidance
- Follow the pinned upstream source instructions only after host authorization; package registry availability was not independently checked in this review.
Check finite action authority and atomically commit a five-row gate bundle before a separately controlled outbox dispatcher.
- Primary editorial role
- evidence-and-verification
- Limits / unsupported uses
- Finite audit consistency is not OAuth infrastructure, external truth, physical outcome or exactly-once delivery. Deployment owns identities, durable storage, actuator monitoring and incident response.
- Source reviewed
- 2026-09-24
- Source revision / declared version
- 9449b338c4c8b959878704a48b2f16e291e2dfb8 / 1.1.0
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- v1.1.0 · 2026-07-02T01:04:13Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Strict horizon manifest, writer/issuer identities, log, action request, capacities and risk premises.
- Outputs
- Rejected request or checked atomic bundle; dispatch and actuator acceptance remain separate records.
- Prerequisites
- Python >=3.10; declared scope and host authority.
- Effects and trust boundary
- The committer records decisions without executing an actuator. A separately authorized OutboxBroker can dispatch external actions. This review inspected source only.
- First inspection
- Read the pinned README, contract and failure cases before considering execution.
- Installation guidance
- Follow the pinned upstream source instructions only after host authorization; package registry availability was not independently checked in this review.
Separate claimed completion from finite support, checked finality, unresolved obligations and environment changes.
- Primary editorial role
- evidence-and-verification
- Limits / unsupported uses
- A checked ledger is not a truth oracle or external outcome. Structural migration cannot invent evidence; project-specific modes and freshness policies remain necessary.
- Source reviewed
- 2026-09-24
- Source revision / declared version
- e3a937a4a3f28c4077b5f658d6bfb1fc67ddd8fa / 2.0.0
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- v2.0.0 · 2026-07-02T08:04:35Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Finite claim/support graph, certificates, mode, environment tokens and finality records.
- Outputs
- Mode-scoped admissibility, missing-support codes and transition witnesses.
- Prerequisites
- Python >=3.10; declared scope and host authority.
- Effects and trust boundary
- Ledger and verification operations produce local records and reports; finality of those records is not an external action or observation. This review inspected source only.
- First inspection
- Read the pinned README, contract and failure cases before considering execution.
- Installation guidance
- Follow the pinned upstream source instructions only after host authorization; package registry availability was not independently checked in this review.
Inspect positive/negative synthetic controls and near misses for authority, evidence scope, residuals and repeated model decisions.
- Primary editorial role
- research-validity
- Limits / unsupported uses
- Fixtures and validators were co-developed. Cumulative conditions do not isolate causal effects. Compatibility adapters do not establish equivalence with PIC/FOST/PFG/CCR; no real-world safety or generalization claim.
- Source reviewed
- 2026-09-24
- Source revision / declared version
- eb21fda8ed7bfad9dc33becf2ffcc63285249495 / 0.2.0
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- v0.2.0 · 2026-07-19T12:10:23Z
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Pinned cases, expected accept/reject policy, replication settings and declared model/runtime provenance.
- Outputs
- Fixture-scoped decision metrics, timeout records and explicit validity limits.
- Prerequisites
- Python >=3.11; declared scope and host authority.
- Effects and trust boundary
- Benchmark runs produce local synthetic-case artifacts; optional model experiments can contact configured model services. This review inspected source only.
- First inspection
- Read the pinned README, contract and failure cases before considering execution.
- Installation guidance
- Follow the pinned upstream source instructions only after host authorization; package registry availability was not independently checked in this review.
Examine retry, review cost and escalation load using bounded coding tasks and explicit claim margins.
- Primary editorial role
- research-validity
- Limits / unsupported uses
- Twelve synthetic tasks, one logged run per actual model, and scripted costly review do not measure human approval fatigue or establish production readiness. Positive comparative oversight claims remain fail-closed in the reported setup.
- Source reviewed
- 2026-09-24
- Source revision / declared version
- a814d7e02e52d3c7e2a3ce268e2c1bcc0b5ba43b / unknown
- Review state / レビュー状態
- reviewed_snapshot
- Observed GitHub release
- null — no published GitHub release observed
- Release observation / リリース確認
- 2026-09-24T01:42:41+00:00 · current
- License
- Apache-2.0
- Inputs
- Declared small-task protocol, retry/review budgets, channel costs and transport/audit-distortion margins.
- Outputs
- Workflow metrics and bounded claim status, not a provider leaderboard.
- Prerequisites
- Python version not declared here; declared scope and host authority.
- Effects and trust boundary
- Repair experiments execute local Python functions and write artifacts; optional Gemini/Ollama backends invoke configured model services. This review inspected source only.
- First inspection
- Read the pinned README, contract and failure cases before considering execution.
- Installation guidance
- Follow the pinned upstream source instructions only after host authorization; package registry availability was not independently checked in this review.
Version-bound interoperability
“Tested upstream” attributes native fixture checks to the cited project; none of those packages was executed in this website task. Document inspection, index regression tests and native integration execution are different evidence origins. Direction matters: imports_artifact_from points from consumer to producer; exports_proposal_to points from producer to host. Compatibility is neither transitive nor automatically renewed by a release.
sw-ccr → paper-growth
based_on · documented · source_inspected
Repository cites this research for a bounded role.
3b4702454f732c7a0a9f30d87483384dc8a281eb → 10.5281/zenodo.22604358 / archive 7bd9fe246ae0f5a4bf6564b588c0426b5b7f29bd
citation
A citation does not establish complete implementation.
e-collective-capability-runtime-readme-md
sw-pic → paper-ecpt
based_on · documented · source_inspected
Repository cites this research for a bounded role.
55cd5f219d02f02927e247317156e757b1d5d6da → 10.5281/zenodo.20535654 / archive 7bd9fe246ae0f5a4bf6564b588c0426b5b7f29bd
citation
A citation does not establish complete implementation.
e-percolation-inversion-compiler-readme-md
sw-vek → paper-vet
based_on · documented · source_inspected
Repository cites this research for a bounded role.
4008e311ceb16edd6e74d9f71341a90120c0d046 → 10.5281/zenodo.21147093 / archive 7bd9fe246ae0f5a4bf6564b588c0426b5b7f29bd
citation
A citation does not establish complete implementation.
e-verification-ecology-kit-readme-md
sw-alt → paper-alt
based_on · documented · source_inspected
Repository cites this research for a bounded role.
e0296486bb568fdeeda449dada3bc67753ddfe7f → 10.5281/zenodo.20476200 / archive 7bd9fe246ae0f5a4bf6564b588c0426b5b7f29bd
citation
A citation does not establish complete implementation.
e-alt-foundry-kernel-readme-md
sw-cait → paper-cait
based_on · documented · source_inspected
Repository cites this research for a bounded role.
0ecb3afd2ea1d99cedcabd7a9e01e405ae1808a7 → 10.5281/zenodo.20061296 / archive 7bd9fe246ae0f5a4bf6564b588c0426b5b7f29bd
citation
A citation does not establish complete implementation.
e-cait-certificate-schema-readme-md
sw-cpcf → paper-growth
based_on · documented · source_inspected
Repository cites this research for a bounded role.
340b4899d5b0892e06d7d2c1ab1f1d48df15e981 → 10.5281/zenodo.22604358 / archive 7bd9fe246ae0f5a4bf6564b588c0426b5b7f29bd
citation
A citation does not establish complete implementation.
e-collective-phase-control-fabric-readme-md · e-collective-phase-control-fabric-docs-growth-research-mapping-md
sw-oawm → paper-workflow-library
based_on · documented · source_inspected
Repository cites this research for a bounded role.
414299d4d15b5de434f5fb1ccbb4ba17df9155ff → 10.5281/zenodo.19690749 / archive 7bd9fe246ae0f5a4bf6564b588c0426b5b7f29bd
citation
A citation does not establish complete implementation.
e-observable-agent-workflow-memory-readme-md · e-observable-agent-workflow-memory-docs-theory-sources-md
sw-audit → paper-audit-closed
based_on · documented · source_inspected
Repository cites this research for a bounded role.
1e844d1bca18d7bb298aa198e1250bb07bd7ea44 → 10.5281/zenodo.18728589 / archive 7bd9fe246ae0f5a4bf6564b588c0426b5b7f29bd
citation
A citation does not establish complete implementation.
e-audit-closed-ai-scientist-readme-md
sw-loscr → paper-loscr
based_on · documented · source_inspected
Repository cites this research for a bounded role.
334307b59a4870b90f6162705c793bb5615a555a → 10.5281/zenodo.19836225 / archive 7bd9fe246ae0f5a4bf6564b588c0426b5b7f29bd
citation
A citation does not establish complete implementation.
e-loscr-readme-md
sw-alt → sw-ccr
exports_proposal_to · tested_upstream · upstream_reported
ALT 0.5.0 native open/unleased task parses against CCR 1.8.0; ALT sidecar is additional.
0.5.0 → 1.8.0 / 1591e88e3b05f9b5fb06b2d0c749aad8bc0909be
ccr.task.v0.1, open status, unleased proposal
Custom ALT sidecar admission, leases, rewards and execution are not supplied.
e-alt-foundry-kernel-docs-reuse-interchange-md · e-alt-release · e-alt-native-test
sw-alt → sw-vek
imports_artifact_from · tested_upstream · upstream_reported
Capacity report schema and scope/clock/work-conservation checks on pinned fixtures.
0.5.0 → 1.3.0 / b07998135cb9dccde1e67db3c6ed77fdec847e09
scope, clock, work conservation
Counters are supplied, not replayed; no observed rate or empirical independence.
e-alt-foundry-kernel-docs-reuse-interchange-md · e-alt-release · e-alt-native-test
sw-alt → sw-vek
tested_interchange_with · tested_upstream · upstream_reported
Finite synthetic check demand accepted by the released VEK checker.
0.5.0 → 1.3.0 / b07998135cb9dccde1e67db3c6ed77fdec847e09
native contract, schedule
Host residual/service/unit registration and real observed capacity are absent.
e-alt-foundry-kernel-docs-reuse-interchange-md · e-alt-release · e-alt-native-test
sw-alt → sw-cait
tested_interchange_with · tested_upstream · upstream_reported
Supported complete history passes released analyzer/checker; copies do not create assets.
0.5.0 → 0.2.0 / 7d12bcf0bc4c6eae2acdd177175b6be414a274f6
unique formation, costs, receiver checks, requests/results, withdrawal
Expiry, contradiction, refresh, correction and some parent mappings remain partial; no cost-to-capital or arrival claim.
e-alt-foundry-kernel-docs-reuse-interchange-md · e-alt-release · e-alt-native-test
sw-vek → sw-ccr
exports_proposal_to · documented · source_inspected
Capacity extension accompanies schema-valid candidate task.
1.3.0 → 6d8a30820806044b3a4b18d499fbe89bef83fbf2
ccr.task.v0.1, duration rounding, x_vek_capacity
CCR base schema does not enforce extensions; custom admission and atomic host reservation required.
e-verification-ecology-kit-docs-capacity-interchange-md
sw-cait → sw-vek
imports_artifact_from · documented · source_inspected
Pinned capacity schema preserves counters and rejects a false guarantee fixture.
0.2.0 → 1.3.0 / b07998135cb9dccde1e67db3c6ed77fdec847e09
schema, scope, source digest, work conservation
Original VEK reducer journal is absent; counters are not independently reconstructed.
e-cait-certificate-schema-docs-interchange-md
sw-ccr → sw-alt
imports_artifact_from · documented · source_inspected
CCR growth importer pins ALT 0.4.0 token schema, not the new reuse profile.
1.8.0 → 0.4.0 / b5170dbee93b9183f86570c9b2fa325be9cded51
token identity, dependencies, guard, provenance
Receiver service qualification and newer ALT profile acceptance are not implied.
e-collective-capability-runtime-docs-verified-growth-interchange-md
sw-ccr → sw-pic
imports_artifact_from · documented · source_inspected
Optional provider reports preserve blockers, residuals and candidate-only flags.
1.8.0 → 1.1.0
accepted, settled, blockers, residuals
No index-run interoperability test; PIC acceptance alone cannot settle CCR or authorize dispatch.
e-collective-capability-runtime-interop-pic-md
sw-cpcf → sw-ccr
proposed_integration_with · proposed · editorial
A planner candidate could become host work only through a separately implemented admitted adapter.
1.0.1 → 1.8.0
No executable mapping checked / 実行写像の検査なし
Legacy CCR 1.6.0 inspection is quarantined; no v0.6 promotion mapping or execution authority.
e-collective-phase-control-fabric-docs-adapters-md
sw-alt → sw-oawm
proposed_integration_with · proposed · editorial
Qualified reuse may be relevant input to a future memory adapter.
0.5.0 → 414299d4d15b5de434f5fb1ccbb4ba17df9155ff
No executable mapping checked / 実行写像の検査なし
No adapter or promotion receipt exists in this checked mapping; OAWM requires its own event/manifests/checkers.
e-alt-foundry-kernel-docs-reuse-interchange-md · e-observable-agent-workflow-memory-docs-theory-sources-md
sw-cpcf → paper-consequence
related_concept · documented · editorial
Coupled model uncertainty informs the reading route, without a full theorem-implementation claim.
340b4899d5b0892e06d7d2c1ab1f1d48df15e981 → 10.5281/zenodo.22170023
No executable mapping checked / 実行写像の検査なし
No proof that the software implements the paper residual-product theorem.
e-paper-consequence · e-collective-phase-control-fabric-readme-md · e-collective-phase-control-fabric-docs-epistemic-growth-control-md
Verification funding and accountability
Verification consumes resources even when a result is negative. A deployment context therefore needs an explicit payer, resource owner, authority boundary and responsibility for residual risk. Incentives can otherwise reward output volume while shifting verification costs. This is descriptive context, not a theorem requiring a particular market, insurer or law; a technical package does not create those arrangements.
Sources and maintenance
Publication fields come from works.html through the existing research catalogue; included DOI identities were checked with DataCite. Paper scope was inspected in the public TeX archive. Software observations bind source commits separately from GitHub releases. Japanese explanations are editorial translations; official titles remain unchanged. The registry contains the complete screened inventory and evidence locators. Corrections belong in the website repository. Website prose remains CC BY 4.0; inspected software is Apache-2.0, and bundled paper licenses remain separate.
Scanned: 233 research records; 54 repositories. Selected: 37 resources. Full-text scope review applies only to selected papers; remaining candidate matches are explicitly unresolved in the registry.
- Boundary Exchange / viability: unresolved — No exact Boundary Exchange title/DOI in the scanned catalogue. Do not invent a paper identity.
- CGT bandwidth / availability / comparability supplements: unresolved — Distinct TeX manuscripts exist in the source archive, but only the canonical CGT work is a distinct local catalogue record. Do not collapse supplements or invent DOI bindings.
- OASG 10.5281/zenodo.20107661: resolved_software_kind — DataCite classifies this as Software, matching works.html. Included through the repository, excluded from paper bibliography.
- 10.5281/zenodo.20199440: concept_record_date_discrepancy — CGT concept/series DOI has multiple HasVersion records. Existing catalogue first-publication date is 2026-05-15; current DataCite Issued date is 2026-05-28. The exact version binding of the inspected TeX is unresolved. Bibliography includes only verified title/author/year/DOI; it does not claim the DOI identifies these exact source bytes.
Maintenance / 保守 · Corrections / 訂正