arcridge arcridge

Sundial

sundial

Yes to agent autonomy. Yes to engineering control. Sundial captures staff-engineer judgment as durable Decision Records. Loaded into agent context before work begins. Edited like an inbox. Kept in the repo.

Start using Sundial Read the launch post → Share your experience

Problem

Corrections vanish into chat history. Project context lives in sprawling monolithic markdown files if captured at all.

Solve

Sundial captures each consequential decision as a small, reviewable markdown file in the repo.

project/
  .sundial/
    tags.md
    drs/
      accepted/
        dr-0001-testing-strategy.md
        dr-0014-agent-permissions.md
      candidates/
        cand-0027-error-boundaries.md
        cand-0028-review-gates.md
      rejected/
        cand-0019-global-state.md
      retired/
        dr-0004-legacy-build-tool.md

Workflow

Decision-aware coding autonomy: How it Works

01

Retrieve precedent

Before getting started in design or coding tasks, the agent consults accepted Decision Records.

02

Create candidates

When the agent encounters a consequential choice without precedent, it writes a candidate DR instead of silently inventing a new rule.

03

Review the inbox

The engineer edits candidates in a file-backed Candidate Inbox, accepts or rejects them, and retires older DRs when they no longer apply.

04

Improve future work

Accepted DRs become durable project memory, reducing repeated corrections and making later agent work more consistent with precedent.

Agent-native integration

Easy integration with Claude and Codex

skills

Decision-aware workflows

Sundial installs agent skills for design and implementation so accepted decisions are pulled into the work before patterns are chosen.

candidate inbox

Human review stays explicit

Engineers inspect proposed decisions in files or the VS Code sidebar before anything becomes durable project guidance.

AGENT.md

Project instructions included

Bootstrap updates the repo's agent instruction file so corrections can become candidate records instead of disappearing into chat history.

CLI compatibility

Claude Code + Codex CLI

Off the shelf bootstrap options; one-click project onboarding when using these tools.

Start today

CLI + VS Code Sidebar

install the CLI npm install -g @arcridge/sundial
get the VS Code extension VS Code Marketplace →

Sundial is MVP-stage. Tell us what works and what can be improved.

Principles

How Decision Records are shaped.

  • Corrections become artifacts Pushing back on the agent produces a candidate DR.
  • Any Decision Record Not just architecture. Error boundaries, retry policy, naming conventions.
  • Concise Records stay terse because agents load them into context. Long-form rationale and onboarding text live along side but don't pollute agent context.
  • Domain-scoped retrieval DRs are tagged hierarchically (backend.auth, frontend.forms) so agents only pull what's relevant to the task at hand.
  • Recall over precision Queries match the parents and children as well. Missing a relevant DR is worse than loading an irrelevant one.

Portability

Portable governance with no lock-in.