Sign in

flagon-io/g1t

public

g1t/apps/web/app/lib/roadmap.ts

241 lines11,288 bytesCodeBlame

Pick any line to see why it is the way it is: the commit, the pull request and issue it came from, and what the agent was thinking.

A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales1/**
2 * What a project will have and does not yet: the pages the project menu
3 * shows as Soon, each with a page of its own saying what it will be. One
4 * place, so the menu and those pages never disagree.
5 *
6 * Each entry says what it is for, what it will do, and what to use today,
7 * so a Soon is a promise someone can read, not a greyed-out word.
8 */
9
10export type RoadmapItem = {
11 /** In the address: `/<owner>/<project>/soon/<key>`. */
12 key: string;
13 title: string;
A flat project menu with Code first, views as tabs, and Stripe for every owner14 /**
15 * Where it lives: a project page whose tabs it joins, or the workspace,
16 * for what spans projects (boards, the roadmap, packages, the fleet).
17 */
Observability gets its own page; tabs never overflow18 section: "Code" | "Issues" | "Agents" | "Deployments" | "Observability" | "Security" | "Insights" | "Workspace";
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales19 /** One line, for the menu's tooltip and the page's lead. */
20 summary: string;
21 /** Why it matters, in two or three sentences. */
22 why: string;
23 /** What it will do. */
24 plans: string[];
25 /** What to use until it exists: a project page, by its path under the project. */
26 today?: { label: string; path: string };
27};
28
29export const ROADMAP: RoadmapItem[] = [
30 // --- Work ---------------------------------------------------------------
31 {
Packages, with a container registry on g1t.sh; workspaces deleted whole and kept 30 days; Members for every member32 key: "teams",
33 title: "Teams",
34 section: "Workspace",
35 summary: "Groups of members, given roles on repositories together.",
36 why: "Give a group a role on many repositories at once, mention it, and request its review, instead of adding people one by one.",
37 plans: ["Teams with members and maintainers", "Repository roles for a team", "@team mentions and review requests"],
38 },
39 {
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales40 key: "board",
41 title: "Board",
A flat project menu with Code first, views as tabs, and Stripe for every owner42 section: "Workspace",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales43 summary: "Issues and pull requests as a board, a table or a roadmap, with fields of your own.",
Say what g1t does, not whom it is like44 why: "One view of everything in flight, arranged the way your team thinks about it. Agents move the cards as they work, so the board is never out of date.",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales45 plans: [
46 "Board, table and roadmap views of the same items, saved and shared",
47 "Custom fields: status, priority, size, iteration, dates, anything",
48 "Group and filter by owner, outcome, label, agent or state",
49 "Cards move by themselves as agents open, revise and land changes",
A flat project menu with Code first, views as tabs, and Stripe for every owner50 "Across projects: one board can hold work from any of the workspace's projects",
51 "Attach a board to a project, so it shows on that project too",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales52 ],
53 },
54 {
55 key: "roadmap",
56 title: "Roadmap",
A flat project menu with Code first, views as tabs, and Stripe for every owner57 section: "Workspace",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales58 summary: "Outcomes on a timeline, with their dependencies across projects.",
59 why: "An outcome is what should be true when the work is done. On a roadmap you see when each is expected, what it waits on in other projects, and how much has landed.",
60 plans: [
61 "Outcomes as bars on a timeline, from start to target",
62 "Progress from merged work, not from guesses",
63 "Dependencies across projects, drawn from the project graph",
64 "Slip warnings when the work left outgrows the time left",
65 ],
66 today: { label: "Outcomes", path: "plans" },
67 },
68 {
69 key: "milestones",
70 title: "Milestones",
A flat project menu with Code first, views as tabs, and Stripe for every owner71 section: "Issues",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales72 summary: "Dates to land outcomes by, with what is left and what is at risk.",
73 why: "A milestone groups the issues that must land together, by a date. g1t shows what remains and which agent or person holds each part.",
74 plans: [
75 "Issues and outcomes grouped under a due date",
76 "Burn-down from merged pull requests",
77 "At-risk items flagged before the date, not after",
78 ],
79 today: { label: "Issues", path: "issues" },
80 },
81
82 // --- Code ---------------------------------------------------------------
83 {
84 key: "docs",
85 title: "Docs",
86 section: "Code",
87 summary: "Pages about the project that agents keep current as the code changes.",
88 why: "A wiki goes stale the day it is written. g1t's docs live with the code, and when a change makes a page wrong, an agent proposes the fix in the same pull request.",
89 plans: [
90 "Pages written in Markdown, kept in the repository",
91 "Agents update pages a change makes wrong, in the same pull request",
92 "Architecture pages drawn from the code itself",
93 "Search across every project's docs",
94 ],
95 today: { label: "Files", path: "code" },
96 },
97
98 // --- Agents -------------------------------------------------------------
Agents and memory, checks and conflicts, profiles, slug renames, custom domains99 // At work, Sessions and Memory are built (see project-nav.ts), and so is
100 // the workspace's Agent fleet.
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales101 {
102 key: "playbooks",
103 title: "Playbooks",
104 section: "Agents",
105 summary: "How agents should work here: conventions, commands and checks.",
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API106 why: "Every project has its own way of doing things. Today every agent run already reads the repository's AGENTS.md and CLAUDE.md, at the root and in the directories it touches, and reviews read .g1t/review.md, all from the default branch. Playbooks build on those files with structure g1t can act on, not just read.",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales107 plans: [
108 "Instructions per kind of work: fixes, features, reviews, upgrades",
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API109 "Commands to build and test that g1t runs before every change, not just tells the agent about",
110 "Paths agents may not touch without a person, enforced on push",
111 "Learned from reviews: what people corrected becomes a proposed rule",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales112 ],
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API113 today: { label: "Instructions, on Agents", path: "agents" },
A flat project menu with Code first, views as tabs, and Stripe for every owner114 },
115
116 // --- Deployments ----------------------------------------------------------
117 {
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales118 key: "environments",
119 title: "Environments",
A flat project menu with Code first, views as tabs, and Stripe for every owner120 section: "Deployments",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales121 summary: "Staging, production and others, with approvers and branch rules.",
122 why: "Production and previews exist today. Environments add the rest: staging, QA, per-customer, each with its own variables, approvers and rules for what may deploy there.",
123 plans: [
124 "Named environments with their own variables and secrets",
125 "Required approvers before a deploy",
126 "Branch rules: what may deploy where",
127 "Promote a deployment from one environment to the next",
128 ],
129 today: { label: "Deployments", path: "deployments" },
130 },
131 {
132 key: "releases",
133 title: "Releases",
A flat project menu with Code first, views as tabs, and Stripe for every owner134 section: "Deployments",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales135 summary: "Tagged releases with notes written from what landed.",
136 why: "Release notes from the pull requests and sessions that made the release: what changed, why, and who or what changed it.",
137 plans: ["Notes drafted from merged work", "Assets and checksums attached", "Published to the project's page and a feed"],
138 today: { label: "Commits", path: "commits" },
139 },
Packages, with a container registry on g1t.sh; workspaces deleted whole and kept 30 days; Members for every member140
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales141 {
142 key: "flags",
143 title: "Feature flags",
A flat project menu with Code first, views as tabs, and Stripe for every owner144 section: "Deployments",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales145 summary: "Turn features on per environment or per user, without a deploy.",
146 why: "Ship code dark and turn it on when ready, for some users first, at the edge, with no deploy.",
147 plans: ["Flags read at the edge by deployed apps", "Rollouts by percentage, user or environment", "Flags cleaned up by agents when fully on"],
148 today: { label: "Deployments", path: "deployments" },
149 },
150
151 // --- Security -------------------------------------------------------------
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API152 // The overview, secret scanning and dependency upkeep are built: see
153 // routes/repo/security.tsx.
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales154 {
155 key: "code-scanning",
156 title: "Code scanning",
157 section: "Security",
158 summary: "Code scanned for vulnerabilities on every change.",
159 why: "Scanning on every pull request, with findings explained in the review and fixed by the author's agent.",
160 plans: ["Static analysis on every pull request", "Findings in the review, with a fix", "Baselines so only new findings block"],
161 },
162 {
163 key: "firewall",
164 title: "Firewall",
165 section: "Security",
166 summary: "Rules for who may reach the project's deployed apps.",
167 why: "Deployed apps run on Cloudflare. Rate limits, bot protection and IP rules, per app and environment.",
168 plans: ["Rate limits and bot protection", "IP and country rules", "Password-protected previews"],
169 today: { label: "Deployments", path: "deployments" },
170 },
171
172 // --- Observe ------------------------------------------------------------
173 {
174 key: "logs",
Observability gets its own page; tabs never overflow175 title: "Logs",
176 section: "Observability",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales177 summary: "Requests, errors and CPU time of each deployment, and its logs.",
178 why: "Every deployed app's logs and numbers, by deployment, so a regression points at the change that caused it.",
179 plans: ["Live and searchable logs", "Requests, errors, latency and CPU by deployment", "Compare a preview with production"],
180 today: { label: "Deployments", path: "deployments" },
181 },
182 {
183 key: "errors",
Observability gets its own page; tabs never overflow184 title: "Errors",
185 section: "Observability",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales186 summary: "Errors from the running app, each becoming an issue an agent can take.",
187 why: "An error in production should become a fix, not a dashboard. Each new error is grouped, explained, and turned into an issue with the context an agent needs.",
188 plans: ["Errors grouped with stack and request", "One click to an issue for an agent", "Incidents with a timeline and who was told"],
189 today: { label: "Issues", path: "issues" },
190 },
191 {
192 key: "uptime",
193 title: "Uptime",
Observability gets its own page; tabs never overflow194 section: "Observability",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales195 summary: "Checks that the app answers, from around the world.",
196 why: "Know the app is down before your users tell you, and who was told.",
197 plans: ["Checks from many places", "Alerts by email and webhook", "A public status page"],
198 },
199 {
200 key: "analytics",
201 title: "Web analytics",
Observability gets its own page; tabs never overflow202 section: "Observability",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales203 summary: "Who visits the deployed apps, without cookies.",
204 why: "Visits, pages and referrers for each app, private by design, from Cloudflare's own analytics.",
205 plans: ["Visits, pages, referrers and countries", "No cookies, no personal data", "Per deployment and per preview"],
206 },
207
208 // --- Insights -------------------------------------------------------------
209 {
210 key: "delivery",
211 title: "Delivery",
212 section: "Insights",
213 summary: "Lead time, deploy frequency, change failure rate and time to restore.",
214 why: "The four numbers that say how well a team ships, measured from what actually happened in g1t.",
215 plans: ["DORA metrics from merges and deployments", "Review and queue time", "Trends by week and by project"],
216 },
217 {
218 key: "costs",
219 title: "Costs",
220 section: "Insights",
221 summary: "What the project costs, by agent run, sandbox, build and app.",
222 why: "Usage is charged by the workspace; here it is broken down for one project, so you can see what each part of the work costs.",
223 plans: ["Cost by kind of work and by issue", "Cost per merged change", "Budgets per project"],
224 },
225 {
226 key: "impact",
227 title: "Agent impact",
228 section: "Insights",
229 summary: "How much of the work agents do, and how well.",
230 why: "The share of changes agents author, how often their work lands first time, and where people still step in.",
231 plans: ["Agents' share of merged changes", "First-time pass rate of checks and reviews", "Where people correct agents most"],
232 },
233];
234
235export function roadmapItem(key: string): RoadmapItem | undefined {
236 return ROADMAP.find((item) => item.key === key);
237}
238
239export function roadmapIn(section: RoadmapItem["section"]): RoadmapItem[] {
240 return ROADMAP.filter((item) => item.section === section);
241}