HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
nobulexdev
nobulex
HISTORICAL RECORD2026–2026
nobulexdev / nobulex · Not publicly available

nobulex

Discover this repository through its Hacker News conversations.

3Distinct people
4Mentions
0Explicit recommenders
REPOSITORY AT A GLANCE

What to know before exploring

What it is

A public description has not been verified.

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by 3-hour interval4 dated mentions

Observed mentions: 2026-03-01 22:36:25 UTC to 2026-03-03 15:36:58 UTC.

01232026-03-01 21:00:00 UTC to 2026-03-02 00:00:00 UTC (exclusive): 3 mentions; 1 submissions, 2 commentsMar 1, 21:002026-03-02 00:00:00 UTC to 2026-03-02 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-02 03:00:00 UTC to 2026-03-02 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-02 06:00:00 UTC to 2026-03-02 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-02 09:00:00 UTC to 2026-03-02 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-02 12:00:00 UTC to 2026-03-02 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-02 15:00:00 UTC to 2026-03-02 18:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-02 18:00:00 UTC to 2026-03-02 21:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsMar 2, 18:002026-03-02 21:00:00 UTC to 2026-03-03 00:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-03 00:00:00 UTC to 2026-03-03 03:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-03 03:00:00 UTC to 2026-03-03 06:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-03 06:00:00 UTC to 2026-03-03 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-03 09:00:00 UTC to 2026-03-03 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-03 12:00:00 UTC to 2026-03-03 15:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-03-03 15:00:00 UTC to 2026-03-03 18:00:00 UTC (exclusive): 1 mentions; 1 submissions, 0 commentsMar 3, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Mar 1, 21:002026-03-01 21:00:00 UTC2026-03-02 00:00:00 UTC312
Mar 2, 00:002026-03-02 00:00:00 UTC2026-03-02 03:00:00 UTC000
Mar 2, 03:002026-03-02 03:00:00 UTC2026-03-02 06:00:00 UTC000
Mar 2, 06:002026-03-02 06:00:00 UTC2026-03-02 09:00:00 UTC000
Mar 2, 09:002026-03-02 09:00:00 UTC2026-03-02 12:00:00 UTC000
Mar 2, 12:002026-03-02 12:00:00 UTC2026-03-02 15:00:00 UTC000
Mar 2, 15:002026-03-02 15:00:00 UTC2026-03-02 18:00:00 UTC000
Mar 2, 18:002026-03-02 18:00:00 UTC2026-03-02 21:00:00 UTC000
Mar 2, 21:002026-03-02 21:00:00 UTC2026-03-03 00:00:00 UTC000
Mar 3, 00:002026-03-03 00:00:00 UTC2026-03-03 03:00:00 UTC000
Mar 3, 03:002026-03-03 03:00:00 UTC2026-03-03 06:00:00 UTC000
Mar 3, 06:002026-03-03 06:00:00 UTC2026-03-03 09:00:00 UTC000
Mar 3, 09:002026-03-03 09:00:00 UTC2026-03-03 12:00:00 UTC000
Mar 3, 12:002026-03-03 12:00:00 UTC2026-03-03 15:00:00 UTC000
Mar 3, 15:002026-03-03 15:00:00 UTC2026-03-03 18:00:00 UTC110

What Hacker News says

4 sources
arian_·Mar 3, 2026Submission

Show HN: I built a way to prove your software kept its promises

Software makes commitments all of the time. "I won't transfer more than $500," "I'll only access these three APIs," "I won't modify production data." But there is truly no way to verify it actually kept those commitments after the fact. All you do is just trust the logs and which the software itself wrote. I built Nobulex to fix this. It is open-source middleware that does three things: 1. Lets you define behavioral rules in a simple DSL (permit, forbid, require) 2. Intercepts all actions at runtime and blocks anything that will violate the rules 3. Logs everything in a hash-chained audit trail that anyone can independently verify, not just the operator. The key insight: you can't just audit a neural network's reasoning, but what you can do is audit its actions against stated commitments. `verify(rules, actionLog)` is always deterministic
Read the rest
. npm install @nobulex/identity @nobulex/covenant-lang @nobulex/middleware Three packages, three lines to integrate. The rule language is Cedar-inspired: covenant MyAgent { permit read; forbid transfer where amount > 500; require log_all; } Site: nobulex.com | 6,100+ tests across 61 packages. MIT licensed. I'd love feedback on the rule language — is the permit/forbid syntax intuitive, or would you design the DSL differently? I'm 15 and built this solo. Happy to answer anything about the architecture.
1 points · Open discussion
Based off of all the feedback here, I have built a quick demo that shows the multi-party use case on why cryptography matters when a third party needs to verify compliance independently: https://github.com/nobulexdev/nobulex/blob/main/demo/two-par... Run it: npx tsx demo/two-party-verify.ts Three steps: operator creates a covenant, claims compliance and then a regulator verifies the cryptographic proof without trusting the operator. That is the core of what Nobulex does. Everything else is tooling around this pattern. Appreciate the pushback, as it helped clarify what actually matters.
In Show HN: I'm 15. I mass published 134K lines to hold AI agents accountable
You also published all strategy documents, all internal project plans, even the marketing/adoption plan. https://github.com/nobulexdev/nobulex/blob/main/docs/crisis-... "HN Posting Notes Internal only. Delete before posting. When posting UNCOVENANTED-AGENT-PROBLEM-HN.md: Post on Tuesday or Wednesday, 8-9am EST Title is just: "The Uncovenanted Agent Problem" Replace [GitHub link] with actual repo URL when live under Kova name First comment should be from you: brief context on who you are and why you built this Respond to EVERY comment in the first 6 hours Don't be defensive. Thank critics. Ask follow-up questions. If someone finds a real flaw, acknowledge it publicly and say you'll address it DO NOT mention your age unless directly asked. Let the work speak. " > DO NOT mention your age unless directly asked.
Read the rest
Let the work speak. I'd agree. Why does the age matter.
In Show HN: I'm 15. I mass published 134K lines to hold AI agents accountable

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.