Laya Gate | Private Daily Work Brief for Obsidian

Laya Gate is a private Obsidian add-on. I built it for owners and operators whose commitments are spread across notes, clients, contractors, and time zones. The local Python sidecar reads the Markdown vault you approve, finds tasks, deadlines, handoffs, risks, and approval blockers, then writes a brief you can review inside Obsidian.

Every item keeps the source note, the line, and the reason next to it. A finding is never just a claim.

I run a native Obsidian command. No second app, no cloud round trip.

A local Python sidecar does the reading. It picks up dates, tasks, handoffs, risks, and open approvals, and it keeps the source path, the line, and a short quote for every item it surfaces.

Then the Obsidian plugin writes a brief you can open right there in the vault.

The current synthetic demo scans 12 notes. It returns 1 item for attention, 8 for review, 3 low signal, 0 warnings, and every surfaced item carries evidence.

The generated note shows the heading, the scanned count, and the source line and quoted evidence under each item. That is the whole point. If I cannot point at the note and the line, it does not go in the brief.

Obsidian does not index hidden folders. The durable copy lived under .laya-gate/output/ and was invisible to the vault, so the plugin could write it but could never open it, and repeated scans started failing with a file-already-exists error.

I kept the hidden durable copy and added an indexed review copy at the vault root, then excluded both from later scans. Without that exclusion the brief starts feeding on its own output.

I did not turn this into a service. The sidecar binds to loopback, it only reads vault roots I allowlist, and it never edits a note. I ran it read-only against my private vault and it surfaced 100 items with 0 warnings, but that vault stays private and none of its content is in this post. Everything above comes from a disposable synthetic vault.

I also did not build an autonomous writer. The model is a bounded ranking and triage layer, not an author. A decision gets recorded so I can review it, and execution stays disabled. Model confidence is not proof, so a weak signal falls back to the deterministic result.

I kept the repository private. This is a product I am still tightening, not a product I am handing over.

The full case study, including the source breakdown and the generated brief, is here: https://laya-gate-case-study.pages.dev

If your work already lives in Obsidian and you keep losing track of what needs a decision today, this is built for that. I am looking for owners, operators, and small studios who want a short, evidence-backed list they can act on, and a hard boundary so nothing gets changed behind their back.

If you want to see it running, or you want to talk about your own vault, send me a message.