Constraint Dynamics  /  Funding
AI safety grant or fellowship · geometric knowledge · strategic infrastructure

Fund geometric knowledge
for safer AI discovery.

The AI safety grant or fellowship is the first funding target. Golem is the implemented research system at the center of that work: a geometric lattice where claims have coordinates, provenance, status, tensions, and temporal history before they ever reach speech. Constraint Native carries the same discipline into governed agent action as the commercial bridge.

01 · The case

Golem leads the research.
Constraint Native carries the bridge.

The work is a safety research program, not only a better MCP gateway. The thesis is concrete: claims become coordinates, geometry reveals what is missing or conflicted, dream cycles test what should crystallize, and speech waits for status.

01 · Grant

Golem is the research system.

The AI safety grant or fellowship application outputs a paper, benchmark, dataset, and evaluation harness for geometric claim status, abstention, proposal leakage, provenance retention, and false crystallization behavior.

02 · Evidence

The system runs today.

Dated lattice metrics, an inspectable app with discovery geometry, an adaptive dream-cycle control loop, the DOI-backed Golem release, and published conceptual lineage behind the work.

03 · Bridge

Constraint Native translates the discipline.

The agent firewall is the buyer-facing surface: governed action, policy gates, approvals, taint tracking, signed proof paths, and offline replay.

02 · The ask

Grant path first.
Bridge-ready underneath.

One evidence package supports the grant application, then Foresight, NSF SBIR, microgrant diligence, and strategic infrastructure conversations. The near-term work is to make Golem's evidence — app, lattice metrics, claim-coordinate diagrams, discovery behavior, dream-cycle states, and benchmark plan — easy for an outside reviewer to read in one sitting.

Track A · AI safety grant or fellowship

Research audience, grant framing.

Track A is the grant path: Golem as the implemented testbed for verification before voice, abstention, provenance retention, proposal separation, contradiction preservation, and false crystallization measurement.

The ask is time and focus: finish the application, refresh lattice metrics, capture reviewer-ready app evidence, specify the benchmark, and prepare the Golem paper appendix without broadening the claim.

Vehicle · grant / stipend / research support Audience · AI safety reviewers Output · paper, dataset, evaluation harness
Track B · Bridge funding

Organization runway, $50-100K bridge.

Track B is the practical bridge: a grant, microgrant, or strategic check that keeps the research organization moving while Golem evidence is made reviewable and Constraint Native proof artifacts stay current.

The packet is sized for diligence: use of funds, 12-month budget, Golem evidence map, proof sample, refresh plan, and direct founder contact at matthewacator@gmail.com.

Vehicle · grant / microgrant / strategic check Amount · $50-100K Output · grant submission plus funder-ready packet
03 · What exists now

Working proof,
not a deck.

Funding accelerates what is already visible: the Golem app, dated lattice metrics, the discovery engine's geometry, dream-cycle behavior, the DOI-backed Golem release, the conceptual lineage behind it, and the macOS-first governed agent boundary. The next dollar makes the safety-evaluation evidence easier to review, not the story broader.

evidence funding-readiness current
Golem appClaim Studio, Evidence Cockpit, Discovery Engine, Hypothesis Engine, Anomaly/Analogy, Expectations, Silence Map, Lattice Graph, Oracle Chat, Activity River, Dream Theatre.working
Geometric architectureClaims carry coordinates, embeddings, domain placement, provenance, status, tension state, volatility, immutability, and temporal history.lattice
Lattice snapshot12,725 verified lattice nodes · 11,830 active verified nodes · 215 immutable verified nodes · 5 verified nodes in tension · 23 proposed nodes · 43 verified domains.observed
Benchmark planGrant deliverable: paper, dataset, and evaluation harness for false crystallization, proposal leakage, abstention precision, provenance retention, and contradiction preservation.planned
Discovery engineActive evidence seeking, crystallization of supported claims, rejection of unsupported proposals, preserved tensions, and recycled unresolved contradictions across cycles.engine
Dated evidence caveatLive counts and app captures should be re-run immediately before grant, fellowship, or reviewer submission.refresh
Adaptive control loopMutation timeline shows dream-threshold adjustments, embedder retrains, and coherence-floor moves with named causes.control
Primary paperThe Outlines of Sanity: Constraint-Native Inference in Minds and Machines · DOI 10.5281/zenodo.19658730 · published 2026-04-20.Golem
Conceptual lineageThe earlier Constraint Dynamics Zenodo record remains background theory; it is not the evidence lead for this funding path.lineage
Commercial bridgeConstraint Native — governed coding-agent boundary with signed proof paths.bridge
Proof shapeSample signed proof path: 11 events · 4 policy blocks · 2 quarantines · 1 denied write · 1 denied network · 1 canary block · ed25519 chain.sample
Reviewer artifactsSample proof JSON, blast-radius report, replay-audit walkthrough.artifacts
Supporting architecturePersonal Mirror / OMP · OCP · Open Context Protocol · Resonance Region · proposed Golem Network.stack
Near-term workTrim application fields, capture fresh app evidence, rerun lattice metrics, polish the follow-on packet.next
claim discipline: bounded · local-first · proof-led reviewer-ready after refresh
04 · Reviewer artifact

A clean reviewer bundle
already exists.

A clean reviewer-facing Golem Physics bundle already exists, separate from the live lab workspace. The bundle is a copy-only artifact: useful for diligence because it keeps source, notes, runtime evidence, validation summary, manifest, and checksums in one bounded review surface.

Source

Copied operational source.

The reviewer surface includes copied source and grant-facing docs without asking reviewers to navigate the live lab workspace.

Notes

Curated Obsidian export.

The long-form design record is carried into the packet as curated notes, so the theory, architecture, and reviewer trail stay readable.

Evidence

Runtime evidence preserved.

Runtime evidence, validation summary, manifest, and checksums make the package inspectable without turning the public website into the artifact itself.

reviewer-bundlecopy-only artifact available on request
BoundaryLive lab workspace kept separate from reviewer evidence; the bundle is a bounded copy for review, not the runtime itself.separate
ContentsCopied source, curated Obsidian export, grant summaries, full runtime evidence, validation summary, manifest, and checksums.packet
What it showsPackaging discipline and inspectability: the work is not only a pitch deck, and reviewers have a clear artifact path.discipline
What funding doesRefresh, redact, rerun metrics, package the benchmark, and turn the bundle into a submission-grade AI safety grant or fellowship artifact.refresh
reviewer-ready after refresh · not a completed benchmark result request access via funding packet
05 · Use of funds

Turn the working system into
externally reviewable evidence.

The immediate work is not to invent the research program. It is to make the evidence legible enough that grant reviewers, funders, and strategic backers can understand Golem as an implemented geometric knowledge system, then underwrite the next phase with confidence.

fundingwhat funding unlocks $50-100K
Evidence path$50-100K funds refreshed Golem metrics, reviewer screenshots, benchmark specification, fresh Constraint Native proof export, external security review scope, grant/fellowship submissions, and a funder-ready packet.unlock
0-10 daysFinal grant/fellowship submission.submit
10-30 daysFresh Golem evidence plus Constraint Native proof export.refresh
30-60 daysBenchmark spec plus reviewer bundle.bundle
60-90 daysFollow-on grants, external review, and commercial bridge polish.bridge
Track 01

AI safety grant or fellowship package

Finalize the "Verification Before Voice" application: tighten the prose to exact form limits, add applicant details and references, rerun lattice metrics, and keep the proposal focused on measurable safety evaluation.

→ submit first
Track 02

Golem app and discovery-engine evidence

Capture reviewer-ready walkthrough notes and screenshots for Claim Studio, Evidence Cockpit, Discovery Engine, Hypothesis Engine, Anomaly/Analogy, Expectations, Silence Map, Lattice Graph, Oracle Chat, Activity River, Dream Theatre, mycelium/temporal memory, and the mutation timeline.

→ inspectable
Track 03

Benchmark plan

Design the full benchmark: specify false crystallization, proposal leakage, abstention precision, provenance retention, temporal correctness, contradiction preservation, and useful-answer rate as measurable targets. Produce the paper, dataset, and evaluation harness.

→ evaluation plan
Track 04

Theory and paper appendix

Present the published Constraint Dynamics theory and the Golem release as the conceptual foundation. Keep implemented single-system claims separate from proposed network extensions.

→ credibility layer
Track 05

Foresight and NSF follow-ons

Adapt the packet for Foresight AI for Science & Safety and NSF SBIR. Shift emphasis from grant outputs toward reproducible infrastructure and commercialization.

→ non-dilutive capital
Track 06

Constraint Native commercial bridge

Keep the agent firewall materials current as the commercial bridge: demo, proof export, threat model, and buyer-readable positioning that follows the research proof.

→ commercial path
06 · Funder order

Submit in the order
the case is sharpest.

The first application is narrow and research-led. Later paths widen toward AI-for-science, safety infrastructure, cybersecurity, and commercial translation.

Target · 01

AI safety grant or fellowship

Golem as safety evaluation: abstention, provenance, proposal leakage, contradiction preservation, false crystallization, and benchmarkable behavior — implemented today, measurable through the grant work.

Target · 02

Foresight AI for Science & Safety

Golem as epistemic infrastructure for AI-assisted science: hypothesis generation, anomaly surfacing, and analogy bridging without promoting proposals into verified belief.

Target · 03

NSF SBIR / STTR

Translation into trustworthy AI infrastructure with commercial potential: reproducible evaluation, customer discovery, and product hardening for Constraint Native.

Target · 04

Cybersecurity grants

Constraint Native as agent-era endpoint governance: prompt-injection containment, local policy gates, signed proof paths, and offline replay.

Target · 05

Innovation funders and microgrants

The same evidence packet underwrites runway: app proof, grant calendar, use-of-funds memo, demo artifacts, and commercial-bridge plan.

Target · 06

Strategic infrastructure backers

The longer conversation: Golem as verified memory, Constraint Native as governed action, and the wider verification-first architecture.

07 · 90-day outcomes

A fundable plan with
concrete artifacts.

The success condition is concrete: a reviewer reads the page and walks away understanding Golem as the implemented research system, Constraint Native as its commercial bridge, and the wider architecture as the organization's longer-term direction.

plan90-day · 2026-Q2/Q3 tracking
0-10 daysFinalize the AI safety grant or fellowship submission: applicant fields, references, exact field limits, live-metric rerun, and final claim-discipline pass.→ safety grant
10-30 daysCapture fresh Golem app evidence (including the discovery engine), polish the evidence map, prepare the paper appendix, and begin specifying the full evaluation benchmark.→ evidence
30-60 daysAdapt the packet for Foresight and NSF SBIR while keeping Constraint Native ready as the commercial translation path.→ follow-on
60-90 daysSubmit follow-on grants, refresh the Constraint Native proof export, scope external technical review, and keep a funder-ready use-of-funds packet current.→ runway
scope: artifact-led, not promise-led commit: 2026-04-25
08 · Claim discipline

What this round is, and is not.

Stated explicitly so reviewers do not have to read between the lines.

In this round

  • Finalizing the AI safety grant or fellowship package around Golem
  • Capturing reviewer-ready Golem app and discovery-engine evidence
  • Refreshing live lattice metrics and beginning the full benchmark design
  • Hardening the local Constraint Native boundary on macOS alpha
  • Refreshing the signed proof path and reviewer artifacts
  • External threat-model and security review
  • Updating one-pager, memo, budget, and evidence map

Not in this round

  • Compliance certification (SOC 2, FedRAMP, HIPAA, etc.)
  • Replacement for IAM, EDR, DLP, secure-code-review, or human judgment
  • Perfect prompt-injection containment guarantees
  • Full endpoint isolation or hypervisor-grade sandbox claims
  • Cross-platform GA — alpha-scope until the proof is reproducible
  • Clinical, medical, or consciousness claims; Golem is not a chatbot product
  • A full institutional venture raise as the first public ask
Funding packet · request

Review the Golem evidence,
the commercial bridge,
and the use of funds.

The packet, sized to the funder: the Golem evidence map, one-pager, use-of-funds memo, 12-month budget, funding strategy, support-readiness checklist, and a bounded Constraint Native proof sample.