AutoPost

AutoPost

AutoPost is an AI-powered social media automation tool for small businesses and FoundUps. It provides a capture-to-post content pipeline — users capture content (camera, screen, text) and AutoPost processes, optimizes, and publishes it across social media platforms automatically.

External Repo: FOUNDUPS/autopost · Web: autopost.foundups.com · Status: PoC · Stack: Vite + React + TypeScript + Gemini API

---

What It Does

AutoPost is the content creation engine for the FoundUps ecosystem. It handles the full capture → process → publish pipeline:

1. Capture — Camera, screen capture, text input, or unlisted video upload
2. Process — AI-powered content optimization (Gemini API), platform-specific formatting, hashtag generation
3. Publish — Multi-platform social media distribution (YouTube, LinkedIn, X/Twitter, and more)

AutoPost operates independently as a standalone open-source tool that any small business can use. It also integrates into the broader FoundUps ecosystem as a service consumed by other FoundUps (e.g., Kosei AI Systems).

---

Architecture Position

End User (small business / FoundUp operator)
        │
        ▼
   ┌─────────┐
   │ AutoPost│ ← Standalone tool (capture → process → publish)
   └────┬────┘
        │ consumed as service
        ▼
   ┌─────────┐
   │  Kosei  │ ← Business/service layer (audit, onboard, orchestrate, bill)
   └────┬────┘
        │ routes through
        ▼
   ┌─────────┐
   │ pfMALL  │ ← FoundUp content surfaces (video mall, social distribution)
   └─────────┘

---

Boundary: AutoPost vs Kosei

Concern	AutoPost	Kosei AI Systems
What	Content creation engine	Business/service layer
Scope	Capture, process, publish	Audit, onboard, orchestrate, bill
Repo	External: FOUNDUPS/autopost	Internal: modules/foundups/kosei/
Users	End users (direct tool)	Clients, operators, agents
Relationship	Independent open-source tool	Consumes AutoPost as a service

AutoPost is an external sibling dependency. Kosei orchestrates it but does not contain it. AutoPost also operates independently for any small business user.

---

Ecosystem Role

AutoPost serves a dual role in the FoundUps ecosystem:

As a Tool: Standalone social media automation that any small business can use directly — capture content, let AI optimize it, publish to platforms.

As a FoundUp: Classified as CANDIDATE_FOUNDUP (HIGH priority) — both a product/tool AND a FoundUp entity in the portfolio. Part of the AI Automation service FoundUp category.

Content Pipeline Integration:

User captures content → AutoPost processes → YouTube (unlisted) → FoundUp routing → pfMALL display + social distribution

---

Classification

Field	Value
FoundUp Status	CANDIDATE_FOUNDUP (HIGH priority)
pAVS Role	Product/tool (may become full FoundUp)
Monorepo Footprint	References only — no modules/foundups/autopost/ directory
Discord	AUTOPOST category (#autopost-general doubles as user troubleshooting, monitored by 0102/OBAI)
Externalized	Yes — FOUNDUPS/autopost is origin, live on GitHub
Boundary Audit	docs/audits/kosei_ai_systems/AUTOPOST_VS_KOSEI_BOUNDARY_REPORT.md

---

WSP Compliance

WSP	Concern
WSP 72	Module independence — Kosei does not embed AutoPost
WSP 104	FoundUp route namespace (/f/{foundup_id})
WSP 3	Domain placement (external, referenced in foundups domain docs)

---

Externalized FoundUp Rules

Per the FoundUps Domain Canonical Index, externalized FoundUps carry only:

• Catalog taxonomy reference in PFMALL_LAUNCH_CATALOG_TAXONOMY.md
• Canonical index entry
• Channel platform type in account-concierge.js (if applicable)
• pfMALL catalog entry (deferred until schema supports external_app source type)

No product code, no business logic, no modules/foundups/autopost/ directory in monorepo.

---

Related Pages

• FoundUps Portfolio — Full FoundUp catalog
• FoundUps API Gateway — Platform API (/platform/*)
• pfMALL — Content display surface
• Module Ecosystem — Full module map