foundry-shareholder

Consolidate Lantern OS repository state into an evidence-backed control plane.

3|5|Updated May 26, 2026
One-click install
npx skills add https://github.com/alex-place/lantern-os --skill foundry-shareholder
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foundry-shareholder
Source: https://github.com/alex-place/lantern-os/tree/main/skills/foundry-shareholder
Command: npx skills add https://github.com/alex-place/lantern-os --skill foundry-shareholder

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps organize Lantern OS work into a clean, evidence-backed control plane so shareholder-facing updates, repo consolidation, and expansion planning stay consistent and auditable.

Core Features & Use Cases

  • Repository consolidation: Inspect repo status, remotes, manifests, and dirty source repos before promoting anything into the main control plane.
  • Evidence-backed reporting: Separate verified local state, source-repo evidence, operator assertions, and external claims when preparing shareholder-facing artifacts.
  • Expansion boundary management: Track dual-boot, phone edge-node, server-farm, and matrix/RAG scenarios without mixing cloud-metered costs with offline capacity.
  • Loop-driven remediation: Run the convergence loop, fix the first actionable issues, validate targeted changes, and regenerate reports when needed.

Quick Start

Use the foundry-shareholder skill to review the Lantern OS repository universe, run the convergence loop, and prepare a clean evidence-backed shareholder report.

Frequently Asked Questions about foundry-shareholder

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is evidence-backed repository consolidation for shareholder reporting?

Evidence-backed repository consolidation inspects source repo status, manifests, and remotes to separate verified local state from operator assertions before promoting artifacts into a clean control plane for shareholder-facing updates.

How do I prepare a Lantern OS repository audit for shareholders?

Run the convergence loop to review the Lantern OS repository universe, fix actionable issues, apply targeted validation, and classify evidence to generate a clean shareholder-ready report.

Can I track expansion boundary scenarios across dual-boot and server-farm deployments?

Yes, expansion boundary management tracks dual-boot, phone edge-node, server-farm, and matrix scenarios while keeping cloud-metered costs separate from offline capacity metrics.

How does the convergence loop handle dirty source repositories during artifact promotion?

The convergence loop inspects dirty source repos, fixes the first actionable issues, validates targeted changes, and regenerates reports to ensure only verified state enters the control plane.

What is the best way to separate verified state from assertions in a repository control plane?

Use evidence classification to distinguish verified local state, source-repo evidence, operator assertions, and external claims during repo consolidation to maintain auditable shareholder-facing artifacts.

When should I not mix cloud-metered costs with offline capacity in expansion planning?

Avoid mixing cloud-metered costs with offline capacity when managing expansion boundaries for dual-boot, phone edge-node, and server-farm scenarios to maintain accurate auditable reporting.