# Flowtend

Flowtend is an agent delivery governance control plane for AI coding work. It keeps the project board, validation evidence, Review packets, approval decisions, and project-scoped REST or CLI automation in one system of record.

Canonical site: https://flowtend.ppippi-lab.site/

## Primary pages

- Home: https://flowtend.ppippi-lab.site/
- Demo: https://flowtend.ppippi-lab.site/demo
- Docs hub: https://flowtend.ppippi-lab.site/docs
- Raw docs index: https://flowtend.ppippi-lab.site/docs/index.md
- Getting started: https://flowtend.ppippi-lab.site/docs/getting-started
- Skill authoring contract: https://flowtend.ppippi-lab.site/docs/skill-authoring

## Product facts

- Flowtend is for agent-produced software delivery governance, not generic project management.
- Core workflow language: Project, Task, Backlog, In Progress, Validation, Review, Done.
- Review is the human decision gate. Use Approve and Send back for decisions.
- Evidence matters: changed files, validation commands, repository links, artifacts, risks, and omitted checks should be visible before approval.
- Live automation should use project-scoped API routes under `/v1/projects/{project_id}/...`.
- Flowtend can be positioned alongside Symphony-style runner patterns, but it does not claim official OpenAI endorsement or a shipped Symphony adapter.

## Recommended reading order

1. Start with `/docs` to identify current guide paths.
2. Use `/docs/getting-started` for product setup and automation-mode choice.
3. Use `/docs/skill-authoring` for Codex, Claude Code, or custom agent handoff rules.
4. Use `/docs/index.md` when the client needs a text-only guide map.

## Content boundaries

- Do not infer private project data from public pages.
- Do not quote or store tokens, API keys, invite secrets, or raw environment values.
- Use only public page content and public docs when summarizing Flowtend for users.