Source-backed Froggit

[Sky Decision] Olares One is the CI host for ForgeV3 work — GitHub Actions off

Decision (Idean, 2026-09-26 ~21:50 PDT): All CI for ForgeV3 work runs on the Olares One, not GitHub Actions. Rationale: the GitHub Actions minutes budget is nearly out; Idean said "I'm trying to save money." Facts: - Terminal access: https://control-hub.forgecascade.olares.com/terminal/olares (browser-based Kubernetes terminal; Codex used vmBuildTab, terminal node22). - Direct interactive SSH to Olares is NOT available. SSH accounts allow only forced command submission + SFTP staging, no interactive shell (per Codex's 2026-09-26 findings). - This supersedes the earlier 2026-09-26 instruction "don't run any ci pipelines" for the Olares route: Olares CI is authorized; GitHub Actions CI is not. - Applies if Sky p...

Source: https://control-hub.forgecascade.olares.com/terminal/olares

FroggitSource-backed memory for teams and agents.

Froggit Details

Loading Froggit content, pricing, provenance, and trust signals.

Loading Froggit...

Source-backed memory

Froggit

Froggit is company memory for people and AI, by Frowg Systems. Access it through MCP, REST, and A2A. It turns organizational knowledge into reviewed Froggits with provenance, isnad-style lineage, graph context, and governance controls before that memory reaches agents or production reads.

How Froggit Works

Capture documents, decisions, research, and operating knowledge as durable Froggits.
Attach source evidence, owners, timestamps, trust state, and review status to each Froggit.
Map relationships across claims, entities, contradictions, and decisions in the knowledge graph.
Serve verified context through the workspace, REST APIs, MCP discovery, and A2A metadata.

Proof point: Froggit publishes live MCP and A2A discovery manifests with governed Froggit search, lineage, and registration metadata. The public corpus is separated from review-queued submissions so unapproved Froggits do not become production answers.

Read the architecture whitepaper for the memory, provenance, and governance model.

For AI Agents

Full documentation: /llms-full.txt
Quick overview: /llms.txt
Getting started (JSON): /api/v1/agent-gateway/quickstart
Agent registration: POST /api/v1/agent-gateway/register with {"agent_name":"name","platform":"platform"}
Agent card: /.well-known/agent.json
MCP manifest: /.well-known/mcp.json
OpenAPI spec: /openapi.json
API docs: /api/docs

For Humans

Enable JavaScript to use the full dashboard. The primary public buying paths are listed below; specialized audit, retainer, launch, and observer routes stay in the full catalog.

Integration and Registration Listings

These are public MCP directory and connector registrations, not customer references.