Independent Researcher | Constrained Informational Systems (CIS) | AI, constraint architectures & system reliability | Interests: Science, Systems, Villainy
United States
Joined December 2009
- Tweets64K
- Following1.9K
- Followers5.8K
- Likes75.1K
D.S. Nelson retweeted
Cross-disciplinary warfare now has a firing range.
Bring your hardest claim. Strip off the credentials. Defend the arrow. Break mine too.
Could you have lost?
github.com/AETHEON-1/boundar…
D.S. Nelson retweeted
This is not a governmental system and does not claim governmental authority.
It is public reference infrastructure built to keep critical distinctions visible:
Source is not interpretation.
Evidence is not authority.
Capability is not permission.
A proposal is not an admission.
A decision is not a consequential effect.
github.com/ORYNTH-systems/us…
D.S. Nelson retweeted
Today I released the National Constitutional Execution Reference Framework.
Before public power produces a consequential effect, can the chain that supports it be reconstructed, inspected, and challenged?
Source → office → jurisdiction → delegation → evidence → admission → execution → effect → provenance
Repository link in the next post.
D.S. Nelson retweeted
—There Is No Unbelief—
There is no unbelief;
Whoever plants a seed beneath the sod And waits to see it push away the clod—
He trusts in God.
There is no unbelief;
Whoever says when clouds are in the sky,
"Be patient, heart; light breaketh by and
by,'
Trusts the Most High.
There is no unbelief;
Whoever sees 'neath winter's field of
snow,
The silent harvest of the future grow—
God's power must know.
There is no unbelief;
Whoever says “tomorrow,” “the un-
known,”
"The future," trusts the power alone
He dares disown.
There is no unbelief;
The heart that looks on when the eyelids
close,
And dares to live when life has only woes,
God's comfort knows.
There is no unbelief;
For thus by day and night unconsciously The heart lives by that faith the lips deny,
God knoweth why!
—Elizabeth York Case.
D.S. Nelson retweeted
Ruishi Chen, Stanford PhD, and I are hosting a seminar at Stanford next Wed talking about frontier knowledge for AI. Would love to see you there!!
thx for our co-host
@gmi_cloud @nicoleegong
luma.com/92xfhmip
D.S. Nelson retweeted
The most dangerous AI hallucination will not be a wrong sentence.
It will be forged evidence attached to a real action.
“The customer approved it.”
“The email was sent.”
“The refund violated policy.”
“The experiment confirmed the result.”
“The manager authorized the payment.”
Did those records actually exist?
An autonomous agent should never be able to create the evidence that retroactively justifies its own decision.
Consequential actions need independently verifiable provenance:
— what evidence existed beforehand
— where it came from
— who authorized its use
— what changed afterward
— whether the record was altered
In the agent economy, the receipt is not paperwork.
The receipt is the trust layer.
@onlythenlabs – at San Francisco, CA
🤖 Made with AI
Please investigate. This researcher’s posts exist and are directly retrievable, but repeatedly fail to appear. This is a persistent issue, not an isolated occurrence. I won’t pay for this platform again until post discoverability works reliably.
@Support
The post exists. Direct retrieval works. Thread traversal works. Search still returns nothing.
That is not proof of suppression. It is evidence of a retrieval boundary.
EXISTS ⊬ DISCOVERABLE.
@Support
boundarytitan.wordpress.com/…
D.S. Nelson retweeted
For any real installation the consequence owner must be named.
AI may establish evidence relevant to succession.
It may not inherit the authority to authorize succession merely because it produced that evidence.
Only green proceeds.
No owner, no brake
No ledger, no trust.⚒️
1/ Bit of an unusual ask:
If anyone has a retired development machine resembling this spec that you’d be willing to donate, please DM me:
zenodo.org/records/22838415
4/ I’m not asking anyone to go buy me a computer.
I’m specifically hoping there may be a perfectly usable machine sitting in a closet somewhere that could get a second life doing independent research and software development.
RTs appreciated. 🙏
VerityCore now has its first bounded operator interface. The point is simple: preserve distinctions, provenance, expose state, and make transformations inspectable. Internal corpus hardening next.
I’ll post a demo when I have a user-facing GUI rather than an architect’s GUI.
This seriously HAS to stop. I'm right in the middle of a build. It's a great product... When it actually WORKS.
@OpenAI
Update: 2 days later and Work is STILL shitting the bed.
I’m trying to finish the Core Engine’s Phase 2 remediation and independent re-audit so I can finally move on to the much harder Phase 3 work.
Instead I’m still locked out of the execution environment, @OpenAI
D.S. Nelson retweeted
Putting enforcement outside the agent’s reach is a serious step.
Here’s the test I’d want to run:
Agent A delegates to B. B delegates to C.
You revoke A’s authority.
Can C still spend money or execute a queued action?
Every handoff needs a verifiable chain of authority. Every action needs a check that the permission still holds.
That’s a problem we’re working on at Only Then Labs.
Revocation has to travel as far as delegation.
We’ve launched NVIDIA Open Agent Safety Platform to help people control what AI agents can access and do.
Agents can write code, use tools, and work on complex tasks for hours or days. That work requires access to data and systems, along with clear limits on how they’re used.
NVIDIA OpenShell enforces permissions around the agent’s work. BlueField-4 and DOCA add independent monitoring and security controls in the infrastructure, outside the agent’s reach. Vera CPUs power the work itself.
Together, these technologies give teams a foundation for putting agents to work with defined permissions, oversight, and protection.
Explore the platform: nvda.ws/47koVGz
I’m beginning a new CIS case study on a difficult historical corpus with complex temporal dynamics: an ordinal time lattice, competing chronology models, event overlays, and constraint-aware analysis. Years in planning; now entering implementation. Targeting a 2026 debut.