Hacker News: jithinraj

New comment by jithinraj in "Ask HN: What Are You Working On? (April 2026)"

jithinraj — Mon, 13 Apr 2026 00:40:12 +0000

Working on Originary, built around PEAC, an open protocol for signed interaction records.

The idea is to make agent, MCP, and API interactions verifiable across org boundaries instead of relying only on logs. Still early, but that’s the thing I’m most focused on right now.

Originary: https://www.originary.xyz PEAC: https://github.com/peacprotocol/peac

Show HN: agent logs and what others can actually verify

jithinraj — Sun, 29 Mar 2026 16:06:17 +0000

Article URL: https://whatdidmyagentdo.com

Comments URL: https://news.ycombinator.com/item?id=47564359

Points: 3

# Comments: 0

Show HN: What Did My Agent Do? Compare logs to signed records

jithinraj — Thu, 26 Mar 2026 14:49:32 +0000

Article URL: https://whatdidmyagentdo.com

Comments URL: https://news.ycombinator.com/item?id=47531158

Points: 2

# Comments: 0

New comment by jithinraj in "Show HN: Agent Auditor: verify signed agent, API, and MCP records offline"

jithinraj — Sun, 22 Mar 2026 13:36:40 +0000

Hey HN, I’ve been building Originary, and this is one small piece of it: Agent Auditor.

It opens a signed interaction record and shows who acted, what happened, and whether the signature verifies. You can try it in the browser with a sample file or use the CLI locally. No signup, no backend, no outbound fetches.

I built it because logs are useful for debugging, but not great when another team or customer needs something portable they can inspect independently later. I wanted a simple way to open a signed record and verify it with a public key.

The tool is deliberately narrow: it is read-only, verifies structure and signatures, and does not issue records or validate business logic.

Happy to answer technical questions.

Show HN: Agent Auditor: verify signed agent, API, and MCP records offline

jithinraj — Sun, 22 Mar 2026 13:26:26 +0000

Article URL: https://www.originary.xyz/agent-auditor

Comments URL: https://news.ycombinator.com/item?id=47477304

Points: 1

# Comments: 1

Show HN: Portable signed proof for agent, API, and MCP interactions

jithinraj — Sun, 15 Mar 2026 13:42:39 +0000

Article URL: https://github.com/peacprotocol/peac

Comments URL: https://news.ycombinator.com/item?id=47387314

Points: 1

# Comments: 0

MacBook Neo is a 'shock' to the PC industry: Asus co-CEO

jithinraj — Wed, 11 Mar 2026 05:30:50 +0000

Article URL: https://www.pcmag.com/news/asus-co-ceo-macbook-neo-is-a-shock-to-the-pc-industry

Comments URL: https://news.ycombinator.com/item?id=47332009

Points: 41

# Comments: 3

China's first moon astronauts could land in Rimae Bode

jithinraj — Wed, 11 Mar 2026 05:25:00 +0000

Article URL: https://www.space.com/astronomy/moon/china-first-astronaut-moon-landing-mission-rimae-bode

Comments URL: https://news.ycombinator.com/item?id=47331982

Points: 8

# Comments: 0

New comment by jithinraj in "Show HN: See what your AI agent did and verify it locally"

jithinraj — Tue, 10 Mar 2026 15:19:33 +0000

Agent Auditor is a local browser/CLI tool for opening files describing agent actions and verifying their validity.

I built it because most agent logs are hard to review and easy to fake or misread. This gives you a readable timeline plus local verification for supported receipt/bundle files, with no account and no outbound verification.

Show HN: See what your AI agent did and verify it locally

jithinraj — Tue, 10 Mar 2026 15:17:48 +0000

Article URL: https://www.originary.xyz/agent-auditor

Comments URL: https://news.ycombinator.com/item?id=47324434

Points: 1

# Comments: 1

Show HN: Signed receipts for agent actions

jithinraj — Mon, 09 Mar 2026 13:08:40 +0000

See what your agents did, when, and under what terms.

Comments URL: https://news.ycombinator.com/item?id=47308559

Points: 2

# Comments: 0

TeX Live 2026 is available for download now

jithinraj — Fri, 06 Mar 2026 05:20:10 +0000

Article URL: https://www.tug.org/texlive/acquire.html

Comments URL: https://news.ycombinator.com/item?id=47271187

Points: 95

# Comments: 71

Show HN: Verifiable Interaction Records for Agents

jithinraj — Tue, 03 Mar 2026 15:39:33 +0000

Article URL: https://github.com/peacprotocol/peac

Comments URL: https://news.ycombinator.com/item?id=47234017

Points: 1

# Comments: 0

New comment by jithinraj in "Show HN: Verify and trace OpenClaw tool calls (runnable demo)"

jithinraj — Tue, 10 Feb 2026 19:53:48 +0000

I built a small runnable demo that turns OpenClaw tool-call events into a verifiable trace you can move between systems.

What it does:

- captures tool calls (input/output/timing/status) via the OpenClaw hook surface

- appends them to a tamper-evident chain (each entry links to the previous digest)

- emits a signed, portable receipt per tool call (JSON you can verify offline)

Why: If you’re running agents across services, the “truth” of what happened ends up split across logs. This gives you a single artifact you can attach to an incident, audit, customer ticket, or cross-team handoff.

Try:

- git clone https://github.com/peacprotocol/peac - cd peac && pnpm install - cd examples/openclaw-capture && pnpm demo

It prints a trace + emits 3 example receipts.

Looking for feedback from OpenClaw users: - which fields are missing for real debugging/auditing? - do you want this to map to an existing trace model (OTel, etc.)? - what storage/transport would you actually use for receipts in production?

Show HN: Verify and trace OpenClaw tool calls (runnable demo)

jithinraj — Tue, 10 Feb 2026 19:41:36 +0000

If you’re using OpenClaw, this is a small runnable example that captures tool calls and emits signed, verifiable receipts (tamper-evident chain + receipt output).

Comments URL: https://news.ycombinator.com/item?id=46965661

Points: 1

# Comments: 1

New comment by jithinraj in "Show HN: I made an app that blurs my screen when I slouch"

jithinraj — Sun, 25 Jan 2026 19:03:02 +0000

Such a creative solution to what might seem like a small, but really important, problem! I love how precise and responsive the blur is.

Thanks so much for making Posturr. It definitely deserves more recognition!

New comment by jithinraj in "Show HN: A store that generates products from anything you type in search"

jithinraj — Sat, 13 Sep 2025 19:43:47 +0000

This is a super creative and fun project.

New comment by jithinraj in "Fuck up my site – Turn any website into beautiful chaos"

jithinraj — Fri, 29 Aug 2025 06:23:17 +0000

Does the job well!

New comment by jithinraj in "Web Bot Auth"

jithinraj — Thu, 28 Aug 2025 21:57:44 +0000

Web Bot Auth solves authentication (“who is this bot?”) but not authorization/usage control. We still need a machine-readable policy layer so sites can express “what this bot may do, under which terms” (purpose limits, retention, attribution, optional pricing) at a well-known path, robots.txt-like, but enforceable via signatures.

A practical flow:

1. Bot self-identifies (Web Bot Auth)

2. Fetch policy

3. Accept terms or negotiate (HTTP 402 exists)

4. Present a signed receipt proving consent/payment

5. Origin/CDN verifies receipt and grants access

That keeps things decentralized: identity is transport; policy stays with the site; receipts provide auditability, no single gatekeeper required. There’s ongoing work in this direction (e.g., PEAC using /.well-known/peac.txt) that aims to pair Web Bot Auth with site-controlled terms and verifiable receipts.

Disclosure: I work on PEAC, but the pattern applies regardless of implementation.

New comment by jithinraj in "Who decides the rules of access on the internet?"

jithinraj — Wed, 06 Aug 2025 21:23:59 +0000

Thanks for the thoughtful feedback, fair points all around. Let me clarify:

Who’s driving this: PEAC is open-source (Apache 2.0), started by a small group of developers who care about web standards, but it’s meant to be community-stewarded from the start. No one “owns” it; anyone can contribute, pilot, or join the working group (GitHub or the form). The real goal is collective evolution.

Business model: There isn’t one. It’s pure OSS, free to use or adapt, no strings or monetization. Just focused on enabling fair consent and attribution for everyone.

On “infrastructure”: Good catch. I meant the application layer (CDNs like Cloudflare, content platforms), not lower networking layers. This is about access and content rules, extending things like robots.txt.

On "X”: X is just one option. GitHub issues, HN, email, or the working group form all work (links in repo/blog).

If you or anyone here has thoughts or critiques, I’d love to hear. How would you design the ideal solution?