Repository navigation
Expand file tree
/
Copy pathdocs.html
More file actions
237 lines (224 loc) · 10.9 KB
/
Copy pathdocs.html
File metadata and controls
237 lines (224 loc) · 10.9 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
<title>TaskFlow Documentation</title>
<meta name="description" content="TaskFlow is a team task management system with secure workflows, project tracking, and x402 payment-gated API access for autonomous tools and agents." />
<link rel="icon" href="/static/images/logo.svg" type="image/svg+xml" />
<link rel="stylesheet" href="/static/css/style.css" />
</head>
<body>
<nav class="navbar">
<div class="container">
<a href="/docs" class="navbar-brand"><span>Task</span>Flow</a>
<div class="navbar-nav">
<a href="/docs" class="nav-link active">Docs</a>
</div>
<div style="display:flex; align-items:center; gap:.75rem;">
<a href="https://github.com/Kaybee973/Task-Flow" class="btn btn-ghost btn-sm" target="_blank" rel="noreferrer">Repository</a>
</div>
</div>
</nav>
<main class="docs-shell">
<section class="docs-hero">
<div class="container docs-hero-inner">
<span class="route-pill"><span class="method">project</span> TaskFlow</span>
<h1>TaskFlow Documentation</h1>
<p>
A modern team task management system built in Go, designed for operational clarity,
secure workflows, and programmable integrations for tools and autonomous agents.
</p>
<div class="docs-actions">
<a href="/login" class="btn btn-primary">Open app</a>
<a href="#architecture" class="btn btn-ghost">Explore architecture</a>
</div>
</div>
</section>
<div class="container docs-grid">
<aside class="docs-sidebar">
<div class="docs-sidebar-card">
<div class="sidebar-label">On this page</div>
<a href="#overview">Overview</a>
<a href="#features">Features</a>
<a href="#architecture">Architecture</a>
<a href="#api">API</a>
<a href="#security">Security</a>
<a href="#setup">Setup</a>
<a href="#roadmap">Roadmap</a>
</div>
</aside>
<article class="docs-content">
<section id="overview" class="doc-section">
<div class="section-kicker">Overview</div>
<h2>Built for teams that need order, visibility, and programmable access.</h2>
<p>
TaskFlow combines a clean collaborative dashboard with a robust API layer. It is built to help teams
coordinate delivery, assign work, track progress, and securely expose task operations to external clients,
automation services, and AI-driven tooling without compromising trust or access control.
</p>
<p>
The product emphasizes a practical balance: human-friendly workflows for task coordination and machine-readable
endpoints for external automation. Every major workflow is structured so it can scale from a single team to
multi-project operational environments while preserving a clear foundation for future identity, permissions,
and payment-aware integrations.
</p>
<div class="feature-grid three-up">
<div class="mini-card">
<div class="mini-card-title">Team operations</div>
<p>Projects, task tracking, work status, assignment workflows, and file handling.</p>
</div>
<div class="mini-card">
<div class="mini-card-title">Agent-ready API</div>
<p>Secure, versioned endpoints designed for tools and external systems to interact programmatically.</p>
</div>
<div class="mini-card">
<div class="mini-card-title">Programmable payments</div>
<p>x402-based protection allows API access to be gated via signed payment verification.</p>
</div>
</div>
</section>
<section id="features" class="doc-section">
<div class="section-kicker">Core features</div>
<h2>What TaskFlow provides</h2>
<p>
The system is designed to reduce coordination friction while keeping the technical foundation extensible.
It brings together task visibility, structured project tracking, and API-first integration patterns in one
operational layer.
</p>
<div class="feature-grid">
<div class="mini-card">
<div class="mini-card-title">Task dashboard</div>
<p>Track work by status, urgency, project, and workload across an operational overview.</p>
</div>
<div class="mini-card">
<div class="mini-card-title">Project-based tasking</div>
<p>Group work by project so teams can keep delivery streams organized and visible.</p>
</div>
<div class="mini-card">
<div class="mini-card-title">File attachments</div>
<p>Upload and attach important artifacts to tasks to keep context close to execution.</p>
</div>
<div class="mini-card">
<div class="mini-card-title">Authentication flows</div>
<p>Support for registration, login, logout, and protected browsing routes for authenticated users.</p>
</div>
<div class="mini-card">
<div class="mini-card-title">JSON API</div>
<p>Structured endpoints for create, list, update, and delete operations using clear task payloads.</p>
</div>
<div class="mini-card">
<div class="mini-card-title">x402 enforcement</div>
<p>Protect paid or externally consumed endpoints with signed verification and HTTP 402 challenge flows.</p>
</div>
</div>
</section>
<section id="architecture" class="doc-section">
<div class="section-kicker">Architecture</div>
<h2>Service design and runtime model</h2>
<div class="architecture-box">
<div class="arch-layer">
<div class="arch-pill">Web UI</div>
<p>HTML dashboards, auth pages, task detail pages, and profile management.</p>
</div>
<div class="arch-layer">
<div class="arch-pill">HTTP Router</div>
<p>Go net/http mux handles user pages, static assets, health checks, and API paths.</p>
</div>
<div class="arch-layer">
<div class="arch-pill">Service Layer</div>
<p>Business logic validates task creation, updates, and status transitions.</p>
</div>
<div class="arch-layer">
<div class="arch-pill">Storage Layer</div>
<p>Pluggable TaskStore abstraction supports in-memory usage and PostgreSQL-backed persistence.</p>
</div>
<div class="arch-layer">
<div class="arch-pill">Protection Layer</div>
<p>x402 middleware enforces payment or signed access requirements on external API routes.</p>
</div>
</div>
</section>
<section id="api" class="doc-section">
<div class="section-kicker">API</div>
<h2>Endpoints and usage patterns</h2>
<table>
<thead>
<tr>
<th>Method</th>
<th>Route</th>
<th>Purpose</th>
</tr>
</thead>
<tbody>
<tr><td>GET</td><td>/healthz</td><td>Health and uptime check</td></tr>
<tr><td>GET</td><td>/dashboard</td><td>Main task dashboard</td></tr>
<tr><td>GET</td><td>/tasks</td><td>Task listing UI</td></tr>
<tr><td>POST</td><td>/tasks</td><td>Create a task</td></tr>
<tr><td>GET</td><td>/tasks/{id}</td><td>Task detail page</td></tr>
<tr><td>POST</td><td>/tasks/{id}</td><td>Update task</td></tr>
<tr><td>POST</td><td>/api/tasks</td><td>Create task via protected API</td></tr>
<tr><td>GET</td><td>/api/projects/{id}/tasks</td><td>List tasks for a project</td></tr>
<tr><td>PUT</td><td>/api/tasks/{id}</td><td>Update task via API</td></tr>
<tr><td>DELETE</td><td>/api/tasks/{id}</td><td>Delete task via API</td></tr>
</tbody>
</table>
<div class="code-block">
<pre>curl http://localhost:8080/api/projects/proj-123/tasks \
-H "PAYMENT-SIGNATURE: <base64-encoded-signature>"</pre>
</div>
</section>
<section id="security" class="doc-section">
<div class="section-kicker">Security and access control</div>
<h2>Designed for secure access and verifiable API use</h2>
<p>
TaskFlow keeps the app layer straightforward while adding strong developer-facing controls. The web UI routes
are separated from the machine-readable API, and the protected API endpoints enforce x402-level challenge and
signature verification before returning data.
</p>
<ul class="bullet-list">
<li>Session-aware web routes for authenticated human users</li>
<li>Structured JSON error responses for API callers</li>
<li>ECDSA-based verification for x402 payment signatures</li>
<li>Domain-specific business validation for task creation and updates</li>
<li>Graceful shutdown and structured JSON logging for operations visibility</li>
</ul>
</section>
<section id="setup" class="doc-section">
<div class="section-kicker">Setup</div>
<h2>Run locally</h2>
<div class="code-block">
<pre>git clone https://github.com/Kaybee973/Task-Flow
cd Task-Flow
go run main.go
# then open:
# http://localhost:8080/dashboard</pre>
</div>
<div class="info-grid">
<div class="mini-card">
<div class="mini-card-title">Default behavior</div>
<p>Runs with an in-memory task store, which is ideal for local demos and early validation.</p>
</div>
<div class="mini-card">
<div class="mini-card-title">PostgreSQL</div>
<p>Set DATABASE_URL to enable durable, production-style storage for task persistence.</p>
</div>
</div>
</section>
<section id="roadmap" class="doc-section">
<div class="section-kicker">Roadmap</div>
<h2>Planned evolution</h2>
<ul class="bullet-list">
<li>Real user auth with secure session management and password hashing</li>
<li>Database-backed users, projects, and team permissions</li>
<li>Real-time task updates and notifications</li>
<li>Enhanced moderation, filtering, and search</li>
<li>Expanded payment integrations and client SDKs</li>
<li>Production readiness improvements around deployment and observability</li>
</ul>
</section>
</article>
</div>
</main>
</body>
</html>