LedgerInfra
Menu

ORGANIZATIONAL INVESTIGATION INFRASTRUCTURE

Start every investigation from what your team already found.

Publish AI-generated HTML as a private Slide, have a person review a fixed version, and let the next authorized agent task retrieve that source. Your agents work through the led CLI; people manage the Organization in the Web.

  • Free plan, no card required
  • Versioned HTML is the source
  • Same rules in Web and CLI

design-proposal.htmlSample workflow

  1. 01
    v1 · privatePublish the sample proposal privately7-day retention · export_job_id idempotency · max 2 workers
  2. 02
    v2 · same SlideUpdate the same Slide to 30-day retentionA new fixed version is added; the v1 fixed URL stays as it was
  3. 03
    reviewedA person reviews fixed v2Read the exact version the next task will cite
  4. 04
    next taskA new AI task fetches v2 and uses itIt cites the fixed URL; you confirm the constraints were applied
Illustrative sample. Search or fetch alone is not approval: a person confirms the new task cited the reviewed version.

Web · /explore

Manage the Organization in the Web

After you sign in with a verified email, /explore is where people manage the Organization. The Web is one way in, not the only one.

  • Workspaces
  • Members & sharing
  • Agent access
  • Billing

CLI · led

Operate with the led CLI and your agents

Ordinary work stays agent-first: Codex or Claude Code run led with the shared Agent Skill and stable --json output.

  • led loginSign in and approve the CLI in your browser
  • led publishPublish HTML as a private Slide version
  • led fetchSave an authorized fixed version locally

WEB MANAGEMENT · SAME CLI CONTRACT

Manage your Organization in the Web. Keep every operation in the CLI.

After you sign in, /explore is where people review and manage Organizations, Workspaces, sharing, members, Agent access, and Billing. The led CLI stays complete and agent-friendly, with stable --json output. Both paths use the same authorization, version, and plan rules.

Sign up freeLog in to manageCompare Web and CLI paths

Web management opens at /explore after you sign in with a verified email.

  1. Organizations and Workspaces

    Create or archive Workspaces within your plan and check usage against its limits.

    CLIled organization list --json

  2. Sharing and members

    Invite people, set Workspace roles, and choose who opens each Slide. Invite URLs are shown once; nothing is emailed.

    CLIled invite <EMAIL> --workspace <WORKSPACE_KEY> --role <ROLE>

  3. Agent access

    Decide deliberately which agents may read which Workspaces.

    CLIled auth grant --help

  4. Billing

    Contract, Billing admins, ownership transfer, Customer Portal, and Checkout.

    CLIled billing summary --json

What stays true on every path

  • Versioned HTML is the source.Search and Graph lead back to an authorized HTML version.
  • A fixed version is reviewable.It does not change after publishing.
  • Access is scoped.Organization, Workspace, and visibility rules match in Web and CLI.
  • Agents do not decide for you.Approval and decisions stay with people.
Billing and plan changes, stated plainly
  • From Free, choosing Pro, Team, or Business opens Stripe Checkout for the same default Organization. It stays on Free until Checkout completes and the latest Stripe state is synced.
  • From a paid Pro plan, a valid change to Team is not a normal Checkout: it can immediately update the existing Stripe subscription and invoice prorations before a URL is returned. The Web asks you to confirm first; led billing checkout team sends the same request as soon as you run it.
  • Business Checkout currently starts from your default Free Organization.
  • Changing the billing period or Editor capacity of a current subscription is temporarily unavailable.
  • Billing roles are separate from Organization and Workspace roles and do not grant access to Workspace content or metadata.
Billing commands in the CLI reference

Walkthrough · illustrative

From a prior finding to the next investigation

research/retry-analysis.htmlv2

Retry behavior analysis

Duplicate requests follow a timeout in this example.

research/queue-design.htmlv2

Queue design notes

Linked from retry-analysis, section 3.

reports/incident-follow-up.htmlv2

Incident follow-up

Written by an agent. Ready for human review.

Illustrative example

Step 1 of 5

Find an earlier investigation

Start from authorized HTML already published in one Workspace.

Only documents you are authorized to read in that Workspace are in scope.

All examples are illustrative. No hidden inferred dependencies or approval metadata; people decide what is published.

WHAT A PUBLISHED INVESTIGATION KEEPS

Make a technical investigation something the next task can cite.

Keep an exact version to reference, a Workspace scope you set, and a reviewed source you can hand to the next task you authorize.

01
USE CASE 01

Cite a fixed version, not a moving file.

Point to the exact report version an investigation relied on, even while the latest URL keeps changing.

See the release report example
02
USE CASE 02

Keep the scope explicit.

Publish findings into the Workspace you choose, so reviewers can see exactly what is shared and where it lives.

Browse the HTML examples
03
USE CASE 03

Give the next task a reviewed starting point.

When you authorize the next agent task, hand it the reviewed investigation instead of reconstructing the context.

See the coding guidelines workflow

ONE PUBLISHING LOOP

Keep the work visible, versioned, and retrievable.

SINGLE HTML UPLOAD

Keep the artifact your agent actually made.

Upload one HTML file with its CSS, JavaScript, images, diagrams, and interactions intact. LedgerInfra does not fetch remote resources, convert the file, or freeze a runtime dependency into a proprietary format.

slides · reports · interactive demosOpen the HTML examples

LATEST + FIXED VERSIONS

Update the work without breaking the conversation.

Keep one latest URL in the review thread. Use a fixed version URL when a decision, handoff, or agent citation must point to the exact HTML that was seen.

latest URL + /v/{version_key}See the release report

SEARCH RETRIEVAL

Let agents find the source chunk, not just a filename.

Search statically parses authorized saved HTML inside one Workspace and returns the fixed source version for human verification. Script-generated text and remote resources are not indexed.

Free · Pro · Team · BusinessOpen the Quickstart

GRAPH RETRIEVAL

Follow the references already present in the work.

Graph explores one hop of explicit LedgerInfra links and, when requested, the previous or next version in the same Slide lineage.

Pro · Team · BusinessSee the proposal review

RETRIEVAL FOR AGENTS

Find the source. Follow what it points to.

Search is the entry point. Graph continues from a known version. Both stay inside one authorized Workspace and return fixed source URLs.

GRAPH

Trace explicit references and version lineage.

PRO · TEAM · BUSINESS

Start from a Slide or Search query. Graph returns a one-hop view of explicit LedgerInfra links and optional previous or next versions of the same Slide.

  • Incoming and outgoing references
  • Explicit or system provenance
  • Fixed URL for every node
led graph --slide 01K... --include-lineage --json

ORGANIZATION CONTEXT

Give every handoff a shared source.

Put reports, proposals, and coding guidelines in one shared Workspace so a person can review the handoff and the next agent can reuse the authorized source. Every login starts with an Organization and a default Workspace. Free and Pro keep a clear Organization-admin/editor boundary with viewer sharing; Team and Business add the shared Editor-capacity pool.

Explore Team
One Workspace at a timeSearch and Graph do not cross Workspace boundaries
Three Workspace rolesadmin, editor, and viewer
Authorization before retrievalPrivate content stays visible only to its current owner

Connect one selected Workspace to an AI with read-only access. A person can delegate their current read permissions, or an organization can authorize a service account for the same limited access. Private Slides stay out of grants, and the same contract works from a local machine, your own server, CI, or a cloud runtime.

Read the CLI docs

OWNERSHIP, MADE VISIBLE

Fits the tools your team already uses.

Git — code

Source of truth for code and docs.

CI — verification

Builds, tests, and verifies changes.

Orchestrator — execution state

Tracks tasks, runs, and their state.

LedgerInfra — reviewed artifact + source context

Stores reviewed artifacts, links to source, and enables retrieval.

LedgerInfra carries artifact context. It does not schedule, execute, test, merge, deploy, or approve the loop.

PRICING

Start free. Choose capacity as work grows.

Free, Pro, Team, and Business share one Organization plan ladder.

Compare plans
Display prices in
Prices are shown in Japanese yen.

FREE · ORGANIZATION

¥0

Publish and retrieve your first reusable HTML context. No card required.

  • 25 active Slides
  • 20 versions per Slide
  • 1 GB version storage
  • Search included
Start free

PRO · ORGANIZATION

¥1,480/month, tax included

More Organization publishing capacity, plus one-hop Graph retrieval.

  • Unlimited active Slides
  • 10 Organization Workspaces
  • 500 versions per Slide · 25 GB
  • Search + Graph
Get Pro

TEAM · ORGANIZATION

¥2,980/month, tax included

10 Organization Workspaces and 2 Editors included. Add Editors for ¥1,480 each.

  • Unlimited active Slides
  • 1,000 versions per Slide
  • Unlimited viewers · up to 50 Editors
  • Search + Graph
Start Team

BUSINESS · ORGANIZATION

¥5,980/month, tax included

10 Organization Workspaces and 2 Editors included. Add Editors for ¥2,480 each.

  • Unlimited active Slides
  • 5,000 versions per Slide
  • Unlimited viewers · up to 250 Editors
  • 250 GB + 100 GB per additional Editor
Get Business

QUICKSTART

Set up once. Put your work to use again.

Install led and the shared Agent Skill, then ask Codex or Claude Code to publish a sample proposal and reuse its reviewed version in a new task. Get the sample and follow the full walkthrough.

agent + led CLI5 steps
  1. 1
    Check the CLI and sign in$ led --version $ led login
  2. 2
    Publish in your new account’s default Workspace$ led publish ./design-proposal.html --visibility private --json
  3. 3
    Update the same proposal$ led publish ./design-proposal-v2.html --slide <SLIDE_KEY> --json
  4. 4
    Keep latest and fixed versions$ led show <SLIDE_KEY> --json $ led versions <SLIDE_KEY> --json
  5. 5
    Retrieve the reviewed version in a new task$ led fetch <SLIDE_KEY> --version <VERSION_KEY> --output ./reviewed-proposal.html --json

CODEX + CLAUDE CODE / FIRST REUSE

Take one design proposal into your next AI task.

Use a ready-made sample to publish, update, review, and reuse a design decision. Downloads and CLI documentation are available before signup.

You’ll needCodex or Claude Code / macOS or Ubuntu / Debian / a free verified account to publish
Done whenA new AI task uses the reviewed proposal’s constraints and cites its fixed version URL.
  1. 01

    Publish the sample

    Download a fictional design proposal and publish it privately in your default Workspace.

    Open step 1
  2. 02

    Update the same Slide

    Change the retention period and verify that the latest URL stays the same.

    Open step 2
  3. 03

    Review a fixed version

    Compare the first and revised versions, then record the source you reviewed.

    Open step 3
  4. 04

    Reuse it in a new AI task

    Ask a new task to retrieve that fixed version and use its constraints in a retry design.

    Open step 4

FAQ

What to know before you publish.

Is LedgerInfra an AI presentation maker?

No. Codex, Claude Code, or another tool creates the HTML. LedgerInfra publishes, versions, authorizes, and retrieves the finished artifact.

What can I publish?

The current input is one HTML file up to 20 MB. Remote references are not copied or frozen; they remain runtime dependencies of the browser. Slide decks are the primary use case, and reports and interactive demos use the same input contract.

What does Search return?

Search returns authorized HTML chunks, ranking information, Slide and version identifiers, and a fixed version URL. LedgerInfra does not generate an answer from those results.

What does Graph return today?

On Pro, Team, and Business, Graph returns a one-hop view of explicit LedgerInfra references and optional same-Slide version lineage. Every node points to a fixed version.

What is the difference between latest and fixed URLs?

The latest URL follows the newest version under the same slug. A fixed version URL never changes, so it can anchor a review, decision, handoff, or retrieval result.

Who can view and retrieve Workspace HTML?

Workspace membership and artifact visibility are evaluated before content is returned. Public, Workspace-only, and private visibility have different access boundaries; knowing a URL does not grant access. Private content is visible only to its current private owner.

Are Pro and Team successive upgrade tiers?

Free, Pro, Team, and Business are one Organization plan ladder. Free and Pro keep one editor boundary with viewer sharing; Team and Business add the existing Organization member and Editor-capacity model. Choose any paid plan directly from Billing.

What is included on Free?

Free costs ¥0, requires no card, and includes 25 active Slides, up to 20 versions per Slide, 1 GB of version storage, and Search. Graph is available on Pro, Team, and Business.