Skip to content
Sign in

flagon-io/g1t

public
0

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

254 lines11,950 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 {
Navigation: the workspace's own page with tabs, pins and recent in the sidebar69 key: "insights",
70 title: "Insights",
71 section: "Workspace",
72 summary: "How the whole workspace delivers: lead time, reviews, what agents do and what it costs, across every project.",
73 why: "Each project will have its own numbers. The workspace's put them side by side, so you can see which projects ship steadily, where work waits, and where the money goes.",
74 plans: [
75 "Delivery metrics for every project, side by side",
76 "Where work waits: review, the merge queue, checks",
77 "Agents' share of merged changes, and how often it lands first time",
78 "Cost by project, by kind of work and per merged change",
79 ],
80 },
81 {
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales82 key: "milestones",
83 title: "Milestones",
A flat project menu with Code first, views as tabs, and Stripe for every owner84 section: "Issues",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales85 summary: "Dates to land outcomes by, with what is left and what is at risk.",
86 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.",
87 plans: [
88 "Issues and outcomes grouped under a due date",
89 "Burn-down from merged pull requests",
90 "At-risk items flagged before the date, not after",
91 ],
92 today: { label: "Issues", path: "issues" },
93 },
94
95 // --- Code ---------------------------------------------------------------
96 {
97 key: "docs",
98 title: "Docs",
99 section: "Code",
100 summary: "Pages about the project that agents keep current as the code changes.",
101 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.",
102 plans: [
103 "Pages written in Markdown, kept in the repository",
104 "Agents update pages a change makes wrong, in the same pull request",
105 "Architecture pages drawn from the code itself",
106 "Search across every project's docs",
107 ],
108 today: { label: "Files", path: "code" },
109 },
110
111 // --- Agents -------------------------------------------------------------
Agents and memory, checks and conflicts, profiles, slug renames, custom domains112 // At work, Sessions and Memory are built (see project-nav.ts), and so is
113 // the workspace's Agent fleet.
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales114 {
115 key: "playbooks",
116 title: "Playbooks",
117 section: "Agents",
118 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 API119 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 sales120 plans: [
121 "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 API122 "Commands to build and test that g1t runs before every change, not just tells the agent about",
123 "Paths agents may not touch without a person, enforced on push",
124 "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 sales125 ],
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API126 today: { label: "Instructions, on Agents", path: "agents" },
A flat project menu with Code first, views as tabs, and Stripe for every owner127 },
128
129 // --- Deployments ----------------------------------------------------------
130 {
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales131 key: "environments",
132 title: "Environments",
A flat project menu with Code first, views as tabs, and Stripe for every owner133 section: "Deployments",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales134 summary: "Staging, production and others, with approvers and branch rules.",
135 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.",
136 plans: [
137 "Named environments with their own variables and secrets",
138 "Required approvers before a deploy",
139 "Branch rules: what may deploy where",
140 "Promote a deployment from one environment to the next",
141 ],
142 today: { label: "Deployments", path: "deployments" },
143 },
144 {
145 key: "releases",
146 title: "Releases",
A flat project menu with Code first, views as tabs, and Stripe for every owner147 section: "Deployments",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales148 summary: "Tagged releases with notes written from what landed.",
149 why: "Release notes from the pull requests and sessions that made the release: what changed, why, and who or what changed it.",
150 plans: ["Notes drafted from merged work", "Assets and checksums attached", "Published to the project's page and a feed"],
151 today: { label: "Commits", path: "commits" },
152 },
Packages, with a container registry on g1t.sh; workspaces deleted whole and kept 30 days; Members for every member153
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales154 {
155 key: "flags",
156 title: "Feature flags",
A flat project menu with Code first, views as tabs, and Stripe for every owner157 section: "Deployments",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales158 summary: "Turn features on per environment or per user, without a deploy.",
159 why: "Ship code dark and turn it on when ready, for some users first, at the edge, with no deploy.",
160 plans: ["Flags read at the edge by deployed apps", "Rollouts by percentage, user or environment", "Flags cleaned up by agents when fully on"],
161 today: { label: "Deployments", path: "deployments" },
162 },
163
164 // --- Security -------------------------------------------------------------
Agents get guardrails, run credentials, an audit log, a context hub, repository instructions and mentions; security upkeep; snake_case API165 // The overview, secret scanning and dependency upkeep are built: see
166 // routes/repo/security.tsx.
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales167 {
168 key: "code-scanning",
169 title: "Code scanning",
170 section: "Security",
171 summary: "Code scanned for vulnerabilities on every change.",
172 why: "Scanning on every pull request, with findings explained in the review and fixed by the author's agent.",
173 plans: ["Static analysis on every pull request", "Findings in the review, with a fix", "Baselines so only new findings block"],
174 },
175 {
176 key: "firewall",
177 title: "Firewall",
178 section: "Security",
179 summary: "Rules for who may reach the project's deployed apps.",
180 why: "Deployed apps run on Cloudflare. Rate limits, bot protection and IP rules, per app and environment.",
181 plans: ["Rate limits and bot protection", "IP and country rules", "Password-protected previews"],
182 today: { label: "Deployments", path: "deployments" },
183 },
184
185 // --- Observe ------------------------------------------------------------
186 {
187 key: "logs",
Observability gets its own page; tabs never overflow188 title: "Logs",
189 section: "Observability",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales190 summary: "Requests, errors and CPU time of each deployment, and its logs.",
191 why: "Every deployed app's logs and numbers, by deployment, so a regression points at the change that caused it.",
192 plans: ["Live and searchable logs", "Requests, errors, latency and CPU by deployment", "Compare a preview with production"],
193 today: { label: "Deployments", path: "deployments" },
194 },
195 {
196 key: "errors",
Observability gets its own page; tabs never overflow197 title: "Errors",
198 section: "Observability",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales199 summary: "Errors from the running app, each becoming an issue an agent can take.",
200 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.",
201 plans: ["Errors grouped with stack and request", "One click to an issue for an agent", "Incidents with a timeline and who was told"],
202 today: { label: "Issues", path: "issues" },
203 },
204 {
205 key: "uptime",
206 title: "Uptime",
Observability gets its own page; tabs never overflow207 section: "Observability",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales208 summary: "Checks that the app answers, from around the world.",
209 why: "Know the app is down before your users tell you, and who was told.",
210 plans: ["Checks from many places", "Alerts by email and webhook", "A public status page"],
211 },
212 {
213 key: "analytics",
214 title: "Web analytics",
Observability gets its own page; tabs never overflow215 section: "Observability",
A menu shaped by how g1t works, Soon pages for every promise, and sudo for sales216 summary: "Who visits the deployed apps, without cookies.",
217 why: "Visits, pages and referrers for each app, private by design, from Cloudflare's own analytics.",
218 plans: ["Visits, pages, referrers and countries", "No cookies, no personal data", "Per deployment and per preview"],
219 },
220
221 // --- Insights -------------------------------------------------------------
222 {
223 key: "delivery",
224 title: "Delivery",
225 section: "Insights",
226 summary: "Lead time, deploy frequency, change failure rate and time to restore.",
227 why: "The four numbers that say how well a team ships, measured from what actually happened in g1t.",
228 plans: ["DORA metrics from merges and deployments", "Review and queue time", "Trends by week and by project"],
229 },
230 {
231 key: "costs",
232 title: "Costs",
233 section: "Insights",
234 summary: "What the project costs, by agent run, sandbox, build and app.",
235 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.",
236 plans: ["Cost by kind of work and by issue", "Cost per merged change", "Budgets per project"],
237 },
238 {
239 key: "impact",
240 title: "Agent impact",
241 section: "Insights",
242 summary: "How much of the work agents do, and how well.",
243 why: "The share of changes agents author, how often their work lands first time, and where people still step in.",
244 plans: ["Agents' share of merged changes", "First-time pass rate of checks and reviews", "Where people correct agents most"],
245 },
246];
247
248export function roadmapItem(key: string): RoadmapItem | undefined {
249 return ROADMAP.find((item) => item.key === key);
250}
251
252export function roadmapIn(section: RoadmapItem["section"]): RoadmapItem[] {
253 return ROADMAP.filter((item) => item.section === section);
254}