`/knowledge/platforms/`¶

Per-platform reference pages for the infrastructure layers the eco|monetize™ operating system runs on.

What goes here¶

One markdown file per platform. Each file is the canonical reference for that platform: what it is, what runs on it, architectural decisions, credentials, regions, scaling notes, cost posture, backup strategy, and any gotchas.

Platforms are distinct from tools: - Tools (/knowledge/tools/) — SaaS applications you use AS a product - Platforms (this folder) — infrastructure layers things run ON

Examples: AWS, Azure, GCP, Supabase, Cloudflare, Vercel, 1Password, Tailscale, GitHub.

Frontmatter convention¶

---
title: "{Platform Name}"
type: platform
category: {infra-compute | infra-data | infra-security | infra-cdn | infra-devops | other}
vendor: "{Company}"
owner_agent: {agent_id or tbd}
status: {active | evaluating | deprecated}
billing_owner: {agent_id or CEO}
cost_tier: "{free-tier | startup-credits | paid | TBD}"
region: "{us-west-2 | global | N/A}"
docs_url: "{external URL}"
dashboard_url: "{internal or vendor console}"
last_updated: YYYY-MM-DD
seeded_by: {agent_id}
tags: []
---

Page structure¶

# {Platform Name}

## Purpose
_Why we run on this platform. One paragraph._

## What runs on it
_Services, scripts, agents, workloads hosted here._

## Architecture decisions
_Wikilinks to relevant decision records in `/knowledge/decisions/`._

## Cost posture
_Pricing tier, credits applied, monthly burn, budget guardrails._

## Credentials & access
_How agents and humans authenticate. Link to 1Password vault if applicable._

## Backup & disaster recovery
_RTO/RPO, backup schedule, failover plan._

## Owner
_Primary responsible agent and escalation path._

## Related
_Wikilinks to tools running on this platform, SOPs, playbooks._

## Notes
_Gotchas, quirks, version notes, lessons learned._

Dashboard¶

Live catalog at /dashboards/platforms-catalog.md renders via Dataview — grouped by category, showing billing owners, cost posture, and active workloads per platform.

Relationship to tools¶

A tool (say, Apollo.io) can run on zero or more platforms. A platform (say, AWS) can host many tools and scripts. Link them via wikilinks in the Related section of each page.

/knowledge/platforms/¶