diff --git a/docs/.obsidian/app.json b/docs/.obsidian/app.json new file mode 100644 index 0000000..9e26dfe --- /dev/null +++ b/docs/.obsidian/app.json @@ -0,0 +1 @@ +{} \ No newline at end of file diff --git a/docs/.obsidian/appearance.json b/docs/.obsidian/appearance.json new file mode 100644 index 0000000..9e26dfe --- /dev/null +++ b/docs/.obsidian/appearance.json @@ -0,0 +1 @@ +{} \ No newline at end of file diff --git a/docs/.obsidian/core-plugins.json b/docs/.obsidian/core-plugins.json new file mode 100644 index 0000000..639b90d --- /dev/null +++ b/docs/.obsidian/core-plugins.json @@ -0,0 +1,33 @@ +{ + "file-explorer": true, + "global-search": true, + "switcher": true, + "graph": true, + "backlink": true, + "canvas": true, + "outgoing-link": true, + "tag-pane": true, + "footnotes": false, + "properties": true, + "page-preview": true, + "daily-notes": true, + "templates": true, + "note-composer": true, + "command-palette": true, + "slash-command": false, + "editor-status": true, + "bookmarks": true, + "markdown-importer": false, + "zk-prefixer": false, + "random-note": false, + "outline": true, + "word-count": true, + "slides": false, + "audio-recorder": false, + "workspaces": false, + "file-recovery": true, + "publish": false, + "sync": true, + "bases": true, + "webviewer": false +} \ No newline at end of file diff --git a/docs/.obsidian/graph.json b/docs/.obsidian/graph.json new file mode 100644 index 0000000..e21a18d --- /dev/null +++ b/docs/.obsidian/graph.json @@ -0,0 +1,22 @@ +{ + "collapse-filter": true, + "search": "", + "showTags": false, + "showAttachments": false, + "hideUnresolved": false, + "showOrphans": true, + "collapse-color-groups": true, + "colorGroups": [], + "collapse-display": true, + "showArrow": false, + "textFadeMultiplier": 0, + "nodeSizeMultiplier": 1, + "lineSizeMultiplier": 1, + "collapse-forces": true, + "centerStrength": 0.518713248970312, + "repelStrength": 10, + "linkStrength": 1, + "linkDistance": 250, + "scale": 1, + "close": false +} \ No newline at end of file diff --git a/docs/.obsidian/workspace.json b/docs/.obsidian/workspace.json new file mode 100644 index 0000000..2c6b57e --- /dev/null +++ b/docs/.obsidian/workspace.json @@ -0,0 +1,183 @@ +{ + "main": { + "id": "636a27d281398fe3", + "type": "split", + "children": [ + { + "id": "c41fb81829fb2b2d", + "type": "tabs", + "children": [ + { + "id": "8fba877cb69b6c92", + "type": "leaf", + "state": { + "type": "graph", + "state": {}, + "icon": "lucide-git-fork", + "title": "Graph view" + } + } + ] + } + ], + "direction": "vertical" + }, + "left": { + "id": "043aef78f2e8defa", + "type": "split", + "children": [ + { + "id": "ca3c8b02f18f864d", + "type": "tabs", + "children": [ + { + "id": "51eea273d067a704", + "type": "leaf", + "state": { + "type": "file-explorer", + "state": { + "sortOrder": "alphabetical", + "autoReveal": false + }, + "icon": "lucide-folder-closed", + "title": "Files" + } + }, + { + "id": "66d0d9f5112438c7", + "type": "leaf", + "state": { + "type": "search", + "state": { + "query": "", + "matchingCase": false, + "explainSearch": false, + "collapseAll": false, + "extraContext": false, + "sortOrder": "alphabetical" + }, + "icon": "lucide-search", + "title": "Search" + } + }, + { + "id": "7f6d0f5d0e982ad4", + "type": "leaf", + "state": { + "type": "bookmarks", + "state": {}, + "icon": "lucide-bookmark", + "title": "Bookmarks" + } + } + ] + } + ], + "direction": "horizontal", + "width": 300 + }, + "right": { + "id": "a53108dd427f93cb", + "type": "split", + "children": [ + { + "id": "45b9b60f84ec3a73", + "type": "tabs", + "children": [ + { + "id": "91d17d650ebe79db", + "type": "leaf", + "state": { + "type": "backlink", + "state": { + "collapseAll": false, + "extraContext": false, + "sortOrder": "alphabetical", + "showSearch": false, + "searchQuery": "", + "backlinkCollapsed": false, + "unlinkedCollapsed": true + }, + "icon": "links-coming-in", + "title": "Backlinks" + } + }, + { + "id": "78672ad3f4f22d10", + "type": "leaf", + "state": { + "type": "outgoing-link", + "state": { + "linksCollapsed": false, + "unlinkedCollapsed": true + }, + "icon": "links-going-out", + "title": "Outgoing links" + } + }, + { + "id": "6118dbd5f1b25a40", + "type": "leaf", + "state": { + "type": "tag", + "state": { + "sortOrder": "frequency", + "useHierarchy": true, + "showSearch": false, + "searchQuery": "" + }, + "icon": "lucide-tags", + "title": "Tags" + } + }, + { + "id": "5a225945434b1020", + "type": "leaf", + "state": { + "type": "all-properties", + "state": { + "sortOrder": "frequency", + "showSearch": false, + "searchQuery": "" + }, + "icon": "lucide-archive", + "title": "All properties" + } + }, + { + "id": "2ee3d212d6663f5f", + "type": "leaf", + "state": { + "type": "outline", + "state": { + "followCursor": false, + "showSearch": false, + "searchQuery": "" + }, + "icon": "lucide-list", + "title": "Outline" + } + } + ] + } + ], + "direction": "horizontal", + "width": 300, + "collapsed": true + }, + "left-ribbon": { + "hiddenItems": { + "switcher:Open quick switcher": false, + "graph:Open graph view": false, + "canvas:Create new canvas": false, + "daily-notes:Open today's daily note": false, + "templates:Insert template": false, + "command-palette:Open command palette": false, + "bases:Create new base": false + } + }, + "active": "8fba877cb69b6c92", + "lastOpenFiles": [ + "README.md" + ] +} \ No newline at end of file diff --git a/docs/README.md b/docs/README.md index e14337b..a4fcc06 100644 --- a/docs/README.md +++ b/docs/README.md @@ -14,5 +14,5 @@ Documentation in this repository is organized by concern. - `architecture/monolith-contact-architecture.md` - `architecture/turso-env.md` -- `products/task-system/01_prd.md` +- `products/themis-task-system/01_prd.md` - `redesign/projects.md` diff --git a/docs/products/README.md b/docs/products/README.md index d0bcea3..290a509 100644 --- a/docs/products/README.md +++ b/docs/products/README.md @@ -4,4 +4,13 @@ This directory contains product concepts, PRDs, architecture notes, and supporti ## Current Product Areas -- `task-system/` - PRDs and architecture exploration for the structured developer-friendly task system +- `themis-task-system/` - PRDs and architecture exploration for Themis, the structured developer-friendly task system + +## Notable Docs + +- `themis-task-system/07_visual-discovery.md` - first-pass visual direction, screen priorities, and design guidance for Themis +- `themis-task-system/08_stitch-landing-page-prompt.md` - Google Stitch prompt for the Themis landing page exploration +- `themis-task-system/09_stitch-auth-prompts.md` - Google Stitch prompt for Themis sign-in +- `themis-task-system/10_stitch-dashboard-prompt.md` - Google Stitch prompt for the Themis main dashboard visual exploration +- `themis-task-system/11_stitch-projects-overview-prompt.md` - Google Stitch prompt for the preferred Themis projects-first main screen exploration +- `themis-task-system/12_backend-content-model.md` - backend recommendation for markdown-backed content, structured persistence, and revision history in Themis diff --git a/docs/products/task-system/00_overview.md b/docs/products/themis-task-system/00_overview.md similarity index 91% rename from docs/products/task-system/00_overview.md rename to docs/products/themis-task-system/00_overview.md index f5f143d..8d00f8e 100644 --- a/docs/products/task-system/00_overview.md +++ b/docs/products/themis-task-system/00_overview.md @@ -1,8 +1,8 @@ -# Task System Overview +# Themis Overview -## Working Name +## Product Name -Structured Task System +Themis ## Core Problem @@ -19,7 +19,7 @@ Typical friction points: ## Product Intent -Build a simpler, developer-friendly task system that behaves more like a structured operational database than a traditional project management suite. +Build Themis as a simpler, developer-friendly task system that behaves more like a structured operational database than a traditional project management suite. The system should make it easy to: diff --git a/docs/products/task-system/01_prd.md b/docs/products/themis-task-system/01_prd.md similarity index 95% rename from docs/products/task-system/01_prd.md rename to docs/products/themis-task-system/01_prd.md index ab15e94..d1dde76 100644 --- a/docs/products/task-system/01_prd.md +++ b/docs/products/themis-task-system/01_prd.md @@ -1,8 +1,8 @@ -# PRD: Structured Task System +# PRD: Themis ## Goal -Create a task system that reduces friction in defining, documenting, updating, and executing work. +Create Themis, a task system that reduces friction in defining, documenting, updating, and executing work. The system should feel lightweight enough for daily use, but structured enough to support project management discipline and AI-assisted execution. diff --git a/docs/products/task-system/02_architecture.md b/docs/products/themis-task-system/02_architecture.md similarity index 99% rename from docs/products/task-system/02_architecture.md rename to docs/products/themis-task-system/02_architecture.md index 08ea31b..8af4446 100644 --- a/docs/products/task-system/02_architecture.md +++ b/docs/products/themis-task-system/02_architecture.md @@ -1,4 +1,4 @@ -# Architecture Proposal +# Architecture Proposal: Themis ## Recommended Direction diff --git a/docs/products/task-system/03_workflow.md b/docs/products/themis-task-system/03_workflow.md similarity index 98% rename from docs/products/task-system/03_workflow.md rename to docs/products/themis-task-system/03_workflow.md index 0c80b42..661ffea 100644 --- a/docs/products/task-system/03_workflow.md +++ b/docs/products/themis-task-system/03_workflow.md @@ -1,4 +1,4 @@ -# Workflow Design +# Workflow Design: Themis ## Desired Workflow diff --git a/docs/products/task-system/04_agent-integration.md b/docs/products/themis-task-system/04_agent-integration.md similarity index 96% rename from docs/products/task-system/04_agent-integration.md rename to docs/products/themis-task-system/04_agent-integration.md index e5a0b46..89415f3 100644 --- a/docs/products/task-system/04_agent-integration.md +++ b/docs/products/themis-task-system/04_agent-integration.md @@ -1,4 +1,4 @@ -# Agent Integration Model +# Agent Integration Model: Themis ## Why Agents Matter Here @@ -69,7 +69,7 @@ Example shape: "requirements": ["capture summary", "capture blocker", "capture next step"], "acceptanceCriteria": ["updates render chronologically", "new updates save without page reload"], "dependencies": ["task detail API"], - "references": ["/docs/products/task-system/03_workflow.md"], + "references": ["/docs/products/themis-task-system/03_workflow.md"], "latestUpdate": { "summary": "API shape is ready.", "nextStep": "Implement frontend composer." diff --git a/docs/products/task-system/05_ux-model.md b/docs/products/themis-task-system/05_ux-model.md similarity index 81% rename from docs/products/task-system/05_ux-model.md rename to docs/products/themis-task-system/05_ux-model.md index fe5c06e..8db6cf9 100644 --- a/docs/products/task-system/05_ux-model.md +++ b/docs/products/themis-task-system/05_ux-model.md @@ -1,4 +1,4 @@ -# UX Model +# UX Model: Themis ## UX Goal @@ -16,7 +16,26 @@ Not closer to: ## Primary Views -### 1. Inbox / Triage View +### 1. Projects View + +Purpose: + +- give a strong first impression +- orient the user across multiple active projects +- make it easy to enter the right workstream before looking at individual tasks + +Should show: + +- project name +- short project summary +- current health or momentum signal +- task counts by execution state +- notable blocker or next-step signal +- recent activity age + +This should become the recommended first screen. + +### 2. Inbox / Triage View Purpose: @@ -31,7 +50,7 @@ Should show: - owner - missing definition markers -### 2. Task Detail View +### 3. Task Detail View Purpose: @@ -50,7 +69,7 @@ Should show: This is the core screen. -### 3. Today View +### 4. Today View Purpose: @@ -63,7 +82,7 @@ Should show: - blocked tasks - stale tasks with no recent update -### 4. Initiative View +### 5. Initiative View Purpose: diff --git a/docs/products/task-system/06_delivery-plan.md b/docs/products/themis-task-system/06_delivery-plan.md similarity index 98% rename from docs/products/task-system/06_delivery-plan.md rename to docs/products/themis-task-system/06_delivery-plan.md index 901144a..a240374 100644 --- a/docs/products/task-system/06_delivery-plan.md +++ b/docs/products/themis-task-system/06_delivery-plan.md @@ -1,4 +1,4 @@ -# Delivery Plan +# Delivery Plan: Themis ## Suggested Phases diff --git a/docs/products/themis-task-system/07_visual-discovery.md b/docs/products/themis-task-system/07_visual-discovery.md new file mode 100644 index 0000000..0595a2c --- /dev/null +++ b/docs/products/themis-task-system/07_visual-discovery.md @@ -0,0 +1,397 @@ +# Visual Discovery: Themis + +## Purpose + +This document translates the current Themis product docs into an initial visual direction for the first design explorations. + +It is based on: + +- `00_overview.md` +- `01_prd.md` +- `02_architecture.md` +- `03_workflow.md` +- `04_agent-integration.md` +- `05_ux-model.md` +- `06_delivery-plan.md` +- `../../branding/personal-brand-prompt.md` + +## Design Reading Of The Product + +The product is not a generic project management dashboard. + +It is a structured work surface for defining, clarifying, and executing tasks with low cognitive load. + +The UI therefore needs to communicate: + +- calm control instead of activity theater +- clarity of definition before execution +- structured operational data instead of chat-like chaos +- lightweight daily use without losing rigor +- human and agent readability from the same source of truth + +## Core Visual Thesis + +Recommended direction for the first visuals: + +**Operational notebook with system-grade structure.** + +This means: + +- editorial calm in spacing and typography +- interface rigor in layout, labels, status, and field grouping +- very limited accent color usage +- low chrome and low decoration +- repeated simple components instead of many custom surfaces + +The product should feel closer to a precise workspace than a management dashboard. + +## Product Personality + +The visual language should feel: + +- deliberate +- exact +- quiet +- modern +- technical without looking like a developer toy + +It should not feel: + +- playful +- crowded +- enterprise-heavy +- colorful by default +- like a generic SaaS template + +## Recommended Visual Direction + +### Direction A: Operational Notebook + +This is the recommended primary route for first mockups. + +Characteristics: + +- bright or softly tinted neutral canvas +- dense information, but with strong whitespace rhythm +- large, clear task titles +- mono metadata rows for status, owner, initiative, dates, and labels +- section blocks with calm separators instead of card overload +- timeline-like update history with concise operational entries + +Why it fits: + +- aligns with the "focused operational notebook" goal +- supports reading and writing equally well +- keeps the task detail view as the core screen +- avoids looking like backlog software from the last decade + +### Direction B: Structured Control Surface + +Good secondary exploration. + +Characteristics: + +- darker neutral surfaces or stronger contrast panels +- more explicit status rails and data grouping +- slightly more console-like density +- stronger use of mono and technical labels + +Risk: + +- can become too tool-like or cold +- may over-emphasize engineering aesthetics over clarity + +### Direction C: Editorial Planner + +Good for marketing or overview screens, but not the best default for V1 app screens. + +Characteristics: + +- more typography-led compositions +- broader spacing +- softer, more narrative layout rhythm + +Risk: + +- may under-serve dense daily operational use + +## First Screens To Design + +## Screen Order For Documentation And Review + +Use this sequence when reviewing or presenting the current Themis visual explorations: + +1. Landing Page +2. Sign In +3. Dashboard +4. Projects Overview + +The initial dashboard exploration confirmed an important risk: when Themis starts from active-task density, the first impression drifts toward an overloaded PM tool. + +Because the user may be managing many projects at the same time, the first screen should orient around projects first, then drill into tasks. + +### 1. Projects Overview + +Goal: + +- give an immediate sense of control across multiple active projects +- create a stronger first impression than a dense task dashboard +- help the user enter the correct workstream quickly + +Must visually emphasize: + +- project name and concise summary +- current health or momentum +- active task counts by state +- most important next step or blocker +- recent activity signal + +Recommended composition: + +- strong page heading and short workspace context +- vertical or masonry-like list of project blocks +- each project block should feel like a calm operational briefing, not a KPI card +- each block should allow quick entry into project detail or active tasks +- optional light sidebar for cross-project signals only if it stays quiet + +### 2. Inbox / Triage + +Goal: + +- turn captured work into defined work quickly + +Must visually emphasize: + +- missing definition markers +- task title and summary +- status and priority at scan speed +- lightweight bulk review rhythm + +Recommended composition: + +- compact top quick-create composer +- filter row below +- vertical list of tasks with definition completeness signal +- right-side preview panel on desktop optional, stacked on mobile + +### 3. Task Detail + +Goal: + +- become the single source of truth for one task + +This should be the second high-fidelity screen after projects overview. + +Must visually emphasize: + +- title, summary, and current status immediately +- progressive definition sections +- visible scope boundaries +- requirements and acceptance criteria as structured lists +- updates and decisions as durable history +- next step as a first-class operational field + +Recommended composition: + +- persistent header with title, status, priority, owner +- primary content column for definition and updates +- secondary rail for metadata, linked items, completeness, dependencies +- update composer visually separated, but always easy to reach + +### 4. Today View + +Goal: + +- show active execution without backlog noise + +Must visually emphasize: + +- ready +- in progress +- blocked +- stale + +Recommended composition: + +- sectional grouping by execution state +- very concise task rows or compact cards +- age of latest update as a key signal + +### 5. Initiative View + +Goal: + +- show grouped work without losing task clarity + +This can stay lower priority for visual exploration round one. + +## Information Hierarchy Rules + +### Level 1 + +- task title +- task status +- current next step + +### Level 2 + +- summary +- problem +- expected outcome +- scope in / scope out + +### Level 3 + +- requirements +- acceptance criteria +- decisions +- update history +- links and relationships + +### Metadata Layer + +- owner +- priority +- initiative +- labels +- timestamps +- agent/human attribution + +The interface should make the difference between core task meaning and supporting metadata obvious at a glance. + +## Core Components For First Visuals + +Keep the component vocabulary intentionally small: + +- page header +- quick-create composer +- filter bar +- task row +- compact status badge +- completeness indicator +- section block +- checklist list +- update composer +- update timeline item +- decision item +- metadata rail block + +This directly follows the existing UX guidance to reuse a small number of components repeatedly. + +## Layout Principles + +- mobile first +- one strong reading column by default +- second column only when it reduces scrolling or improves scan speed +- use separation by spacing, rules, and typography before using filled cards +- avoid nested panel stacks where possible +- preserve a stable layout between read and edit states + +## Draft Visual System Direction + +### Color + +- neutral-first palette +- one restrained accent for interactive or active states +- one warning tone for blockers and missing definition +- status colors should be muted, not saturated + +Suggested posture: + +- background: warm-neutral or cool-neutral, but not pure marketing white +- surfaces: subtle elevation difference only where needed +- text: strong contrast for titles, softer contrast for metadata + +### Typography + +- sans-serif for primary reading +- monospace for metadata, ids, labels, timestamps, and system signals +- bigger task titles than a typical dashboard +- clear distinction between section heading, field label, and body copy + +### Spacing + +- generous outer spacing +- tight internal rhythm for structured lists +- section spacing should communicate task stages clearly + +### Shape + +- low to medium corner radius +- avoid overly rounded playful components +- borders should do more work than shadows + +### Motion + +- quick and subtle +- used mainly for state changes, panel reveals, and save feedback +- no decorative transitions + +## Screen-Specific Notes + +### Inbox / Triage + +- completeness should be visible before opening the task +- missing fields should read as guidance, not error states +- row density should support scanning many items quickly + +### Task Detail + +- problem and outcome should feel like anchor sections near the top +- scope in and scope out should appear as a paired block +- requirements and acceptance criteria should be easy to scan and edit inline +- updates need chronological clarity, not chat bubbles + +### Update Composer + +Use a compact structured pattern: + +- what changed +- blocker +- next step + +This composer should feel operational and fast, closer to a system input than a comment box. + +## Anti-Patterns To Avoid + +- colorful kanban-board aesthetics as the main product identity +- excessive cards inside cards +- heavy left navigation plus crowded top bars plus multiple side panels +- status colors carrying too much meaning alone +- oversized analytics widgets in V1 +- chat-style updates that hide structure +- decorative gradients and startup-marketing polish + +## Recommended First Mockup Sequence + +1. Task detail desktop +2. Task detail mobile +3. Inbox / triage desktop +4. Today view desktop +5. Quick-create interaction states + +Reason: + +The task detail screen is the product's center of gravity. Once that screen is visually solved, the surrounding views can inherit its system. + +## Design Decisions Already Supported By Existing Docs + +- The task detail view is the core screen. +- The UI must stay calmer than typical PM software. +- The product should avoid noisy dashboard patterns. +- Structure should be visible by default. +- Quick capture and quick updates are core workflows. +- Agent-readable data should remain legible to humans. + +## Open Questions Before Hi-Fi Design + +1. Should the first visual exploration lean light mode first, dark mode first, or both in parallel? +2. Should initiatives be visually present in the first round, or deferred behind task-first screens? +3. How prominent should agent-oriented actions be in V1 compared with human-only flows? +4. Should the first version optimize more for solo usage density or for future team readability? + +## Recommendation + +Start with **Operational Notebook** as the main direction and design the **Projects Overview** screen first. + +That path gives Themis a stronger first impression, reflects the reality of managing multiple concurrent projects, and reduces the risk of the product looking like another crowded task dashboard. After that, design the **Task Detail** screen as the operational center of gravity. diff --git a/docs/products/themis-task-system/08_stitch-landing-page-prompt.md b/docs/products/themis-task-system/08_stitch-landing-page-prompt.md new file mode 100644 index 0000000..11afde8 --- /dev/null +++ b/docs/products/themis-task-system/08_stitch-landing-page-prompt.md @@ -0,0 +1,194 @@ +# Google Stitch Prompt: Landing Page + +## Purpose + +This prompt is for the first public-facing landing page exploration of Themis in Google Stitch. + +It should communicate what Themis is, why it exists, and why it feels different from overloaded project management tools. + +It should align with: + +- `00_overview.md` +- `05_ux-model.md` +- `07_visual-discovery.md` + +## Stitch Prompt + +Idea +A landing page for Themis, a calm and structured project management app for software engineers, technical leads, and solo builders who manage many projects at the same time. + +Theme +Calm, precise, and technically mature. Editorial structure mixed with subtle system-interface cues. Neutral-first palette, restrained accents, strong typography, generous spacing, and low visual noise. Avoid generic startup landing page patterns, decorative gradients, playful illustrations, bright SaaS marketing colors, and noisy dashboard mockups. + +Content +Create one landing page for Themis. + +Include: +- a clean header with Themis wordmark, simple navigation, and one primary call to action +- a hero section with a concise headline, short supporting copy, and a product preview area +- messaging that positions Themis as a calmer way to manage multiple projects and structured execution +- a section explaining the main product value: clarity, low cognitive load, project-first organization, and structured task definition +- a product preview section that highlights projects overview as the main entry screen +- a second product preview or feature section that shows task detail as the operational center of gravity +- a short section on how Themis differs from typical noisy PM software +- a final call to action section + +Suggested content direction: +- focus on clarity over busyness +- emphasize multiple concurrent projects +- show that Themis helps users move from project context into clear task execution +- speak in calm, direct, structured language + +The page should feel like: +- a premium product introduction +- a system built for focused technical work +- a serious but modern product + +The page should not feel like: +- a startup marketing template +- a page full of feature cards and badges +- a generic PM landing page +- a sales-heavy SaaS homepage + +Layout guidance: +- strong hero with clear message and one visual anchor +- sections with breathing room and clear hierarchy +- use product previews that feel believable and restrained +- avoid overloading the page with too many features at once +- show confidence through structure, not decoration + +## Short Stitch Prompt + +Idea +A landing page for Themis. + +Content +Create one landing page for Themis, a calm and structured project management app for engineers and technical leads managing many projects at once. Include a clean header, a strong hero with concise copy and a product preview, a section explaining the core value of clarity and low cognitive load, a product preview focused on projects overview, a second preview focused on task detail, a short comparison section showing how Themis differs from noisy PM software, and a final call to action. Keep the design minimal, premium, technically mature, and far away from generic startup SaaS styling. + +## Current Exploration + +### Approved Screen + +![Landing page refined exploration](./assets/landing-page-refined.png) + +### Alternate Light Screen + +![Landing page simplified exploration](./assets/landing-page-simplified.png) + +### Alternate Dark Screen + +![Landing page dark exploration](./assets/landing-page-dark.png) + +### Exported Assets + +- Approved screenshot: `./assets/landing-page-refined.png` +- Approved HTML export: `./assets/landing-page-refined.html` +- Approved Stitch screen: `Themis Landing Page Refined` +- Approved Stitch screen ID: `b13d3a79cf504f64be7250dec3addaae` +- Alternate light screenshot: `./assets/landing-page-simplified.png` +- Alternate light HTML export: `./assets/landing-page-simplified.html` +- Alternate light Stitch screen: `Themis Landing Page (Simplified)` +- Alternate light Stitch screen ID: `c2bc1d2d7ec344cebac3002d8ac46716` +- Alternate dark screenshot: `./assets/landing-page-dark.png` +- Alternate dark HTML export: `./assets/landing-page-dark.html` +- Alternate dark Stitch screen: `Themis Landing Page (Dark)` +- Alternate dark Stitch screen ID: `03e9700517ab4fe697fc2f4ae187f8df` + +## Review + +The landing page direction is now approved. + +The refined light version is the main baseline for Themis. The simplified version remains a useful alternate reference for clarity, and the dark version is a strong variant for future branding exploration. + +### Approved Qualities + +1. the hero is clear and product-focused +2. the overall structure explains Themis quickly +3. the product previews feel more aligned with the approved internal screens +4. the features section is more specific and less generic +5. the page feels calm, premium, and believable +6. the dark variant extends the system without losing the product tone + +### What To Preserve + +1. clear hero promise +2. simple product explanation +3. product-grounded feature language +4. alignment with approved projects and auth directions +5. restrained, technically mature visual tone + +### Documentation Status + +- status: approved baseline direction +- approved light variant: `Themis Landing Page Refined` +- alternate light variant: `Themis Landing Page (Simplified)` +- alternate dark variant: `Themis Landing Page (Dark)` + +### Recommended Structure + +1. Header +2. Hero with one clear promise and one product preview +3. Short explanation of the problem Themis solves +4. Projects Overview product preview +5. Task Detail product preview +6. Simple closing CTA + +### Recommended Copy Direction + +Prefer: + +- `Project management with less noise.` +- `Themis helps you manage multiple projects with clarity.` +- `See projects clearly. Define tasks properly. Keep execution visible.` +- `Built for engineers and technical leads managing parallel work.` +- `Projects, not chaos.` +- `Tasks with definition.` +- `Progress with signal.` + +Avoid: + +- `command center` +- `technical manuscript` +- `ledger architecture` +- `stakeholder velocity` +- `enterprise scale` +- `system is different` + +## Refined Prompt For Next Stitch Pass + +Idea +A landing page for Themis. + +Theme +Calm, direct, and product-focused. Minimal, premium, and technically mature. Neutral palette, restrained accents, strong typography, and low visual noise. Avoid sounding like an infrastructure platform, manifesto, or startup marketing site. + +Content +Create one landing page for Themis, a project management app for engineers and technical leads who manage multiple projects at the same time. + +Include: +- a simple header with Themis, a few normal navigation links, and one primary call to action +- a hero with a very clear headline, one short supporting paragraph, and a product preview based on the approved Projects Overview screen +- a short section explaining the problem: most PM tools create too much noise and make multi-project work harder to manage +- a three-part features or value section, but make it specific to Themis rather than generic marketing language +- a product section focused on Projects Overview as the main entry point +- a product section focused on Task Detail as the place where work becomes clearly defined and execution stays visible +- a short closing CTA + +Use simple, direct language. + +Avoid: +- conceptual platform language +- invented metrics and analytics widgets +- infrastructure-heavy copy +- manifesto-style sections +- generic feature cards or generic value statements +- fake dashboard complexity +- waitlist marketing language + +Layout guidance: +- keep the page shorter and more focused than the current version +- make the hero explain the product quickly +- use the real approved product directions as previews +- make the features section feel product-specific and concrete +- emphasize product clarity over atmosphere +- make the page feel believable, useful, and easy to understand in under one minute diff --git a/docs/products/themis-task-system/09_stitch-auth-prompts.md b/docs/products/themis-task-system/09_stitch-auth-prompts.md new file mode 100644 index 0000000..64d4868 --- /dev/null +++ b/docs/products/themis-task-system/09_stitch-auth-prompts.md @@ -0,0 +1,98 @@ +# Google Stitch Prompt: Sign In + +## Purpose + +This prompt is for the sign-in screen of Themis. + +They intentionally avoid repeating the full visual-system guidance already defined in: + +- `07_visual-discovery.md` +- `10_stitch-dashboard-prompt.md` + +Use the existing product design direction and design system context. + +Scope is intentionally limited to **one screen only** so Stitch can produce a more controlled result. + +## Stitch Prompt + +Idea +A sign-in screen for Themis, a structured project management app used by software engineers, technical leads, and solo builders. + +Content +Create a sign-in screen with: +- Themis brand at the top +- a clear heading and one short supporting sentence +- email field +- password field +- show/hide password control +- primary sign-in button +- secondary link to create an account +- forgot password link +- optional remember me control +- a subtle area for validation and error messages +- a calm, balanced form layout centered on the page +- realistic spacing for desktop and mobile + +The screen should feel focused, calm, exact, and efficient. + +Avoid: +- marketing sections +- testimonial blocks +- feature grids +- social sign-in options unless explicitly needed +- split-screen illustrations unless they are extremely subtle +- crowded layouts or too many competing actions + +Layout guidance: +- one primary form card or panel only +- strong visual hierarchy with the heading, fields, and primary action +- supporting actions should stay visually secondary +- keep the composition minimal and easy to scan +- prioritize form clarity over decoration + +## Short Stitch Prompt + +Idea +A sign-in screen for Themis. + +Content +Create one sign-in screen only. Include the Themis brand, a heading, short supporting text, email field, password field, show or hide password control, remember me option, forgot password link, primary sign-in button, create account link, and a subtle area for validation or error messages. Keep the layout centered, calm, minimal, and highly structured. Avoid marketing content, extra panels, or crowded UI. + +## Current Exploration + +### Screen + +![Themis sign-in exploration](./assets/themis-sign-in.png) + +### Exported Assets + +- Screenshot: `./assets/themis-sign-in.png` +- HTML export: `./assets/themis-sign-in.html` +- Approved Stitch screen: `Themis Sign In (Simplified)` +- Approved Stitch screen ID: `c8ad8798d7d047d184b696eb3cbfd096` + +## Review + +The sign-in direction is now approved for Themis. + +### Approved Qualities + +- the neutral palette is aligned with Themis +- the single-column composition is correct +- the overall restraint avoids generic SaaS auth patterns +- the input styling language fits the product system +- the page feels calm, exact, and product-focused +- the composition is tight enough to keep sign-in fast and clear + +### What To Preserve + +1. a single-column centered layout +2. one quiet primary form panel +3. plain language and straightforward field labels +4. limited secondary actions +5. minimal decoration and no extra marketing sections + +### Documentation Status + +- status: approved direction +- use this screen as the auth baseline for future sign-up, recovery, and verification screens diff --git a/docs/products/themis-task-system/10_stitch-dashboard-prompt.md b/docs/products/themis-task-system/10_stitch-dashboard-prompt.md new file mode 100644 index 0000000..b2928bd --- /dev/null +++ b/docs/products/themis-task-system/10_stitch-dashboard-prompt.md @@ -0,0 +1,99 @@ +# Google Stitch Prompt: Main Dashboard + +## Purpose + +This prompt is for the first visual exploration of Themis in Google Stitch. + +Scope is intentionally limited to the **main dashboard screen only**. + +It should align with: + +- `05_ux-model.md` +- `07_visual-discovery.md` + +## Stitch Prompt + +Idea +A main dashboard screen for Themis, a structured project management app built for software engineers, technical leads, and solo builders. The product helps users define tasks clearly, track execution with low friction, and keep scope, requirements, decisions, and updates visible in one calm operational workspace. + +Theme +Operational notebook with system-grade structure. Calm, precise, modern, and technically mature. Neutral-first palette with restrained accent color. Typography-led layout. High signal-to-noise ratio. Clean spacing, subtle borders, low decoration, and a premium product feel. Avoid generic SaaS dashboard patterns, playful visuals, colorful kanban aesthetics, heavy analytics widgets, decorative gradients, and crowded enterprise UI. + +Content +Design only the main dashboard screen for daily work overview. + +Include: +- a top page header with the Themis brand or workspace label, global search, and a primary quick-create action +- a compact quick-create composer near the top for adding a task with title, short summary, and optional initiative +- a filter and view control row for status, priority, owner, and blocked state +- a main overview area focused on active work, with clear sections for Ready, In Progress, Blocked, and Stale tasks +- task items that show title, short summary, status, priority, owner, latest update age, and definition completeness +- visible markers for missing definition such as missing scope, missing requirements, or missing acceptance criteria +- a secondary side panel or summary rail on desktop for operational signals such as next step, blockers, recent decisions, and task counts +- a calm, structured layout that feels fast to scan and easy to act on + +The screen should feel like: +- a focused operational notebook +- a developer-native control surface +- a lightweight but rigorous task workspace + +The screen should not feel like: +- a noisy enterprise dashboard +- a chat workspace +- a generic startup PM template + +Interaction and layout notes: +- desktop-first composition for the mockup, but keep the layout realistic for responsive behavior +- use one strong primary content area and one lighter secondary rail +- prioritize readability and structure over decorative visuals +- make status and completeness visible at scan speed +- keep cards and panels minimal; use spacing, typography, and dividers before heavy containers + +## Short Stitch Prompt + +Idea +A main dashboard for Themis, a structured task system that helps engineers and technical leads manage active work with clarity, low cognitive load, and structured execution tracking. + +Theme +Calm operational notebook. Neutral palette, restrained accents, typography-led hierarchy, subtle borders, low visual noise, and a technically mature product feel. Avoid generic SaaS dashboard styling. + +Content +Create one main dashboard screen only. Include a top header, quick-create composer, filter row, and main task overview grouped into Ready, In Progress, Blocked, and Stale sections. Each task item should show title, summary, status, priority, owner, latest update age, and completeness markers. Add a secondary summary rail for blockers, next steps, recent decisions, and lightweight metrics. + +## Current Exploration + +### Screen + +![Operational Dashboard exploration](./assets/operational-dashboard.png) + +### Exported Assets + +- Screenshot: `./assets/operational-dashboard.png` +- HTML export: `./assets/operational-dashboard.html` + +### Review Notes + +What is working well: + +- strong visual hierarchy +- calm neutral palette +- clear active-work grouping +- good scanability for task rows +- the overall system tone feels close to Themis + +What is not working well enough: + +- the screen still feels too overloaded for a first impression +- too many simultaneous control points make it drift toward a familiar PM dashboard pattern +- task density dominates too early before the user is oriented across projects + +What to preserve in later iterations: + +- the dashboard structure +- the restrained color usage +- the dense but readable task summaries +- the balance between overview and utility panels + +Recommended conclusion: + +Use this exploration as a reference for tone and component language, but move the next main-screen exploration to a **Projects Overview** entry screen instead of another task-heavy dashboard. diff --git a/docs/products/themis-task-system/11_stitch-projects-overview-prompt.md b/docs/products/themis-task-system/11_stitch-projects-overview-prompt.md new file mode 100644 index 0000000..7330966 --- /dev/null +++ b/docs/products/themis-task-system/11_stitch-projects-overview-prompt.md @@ -0,0 +1,103 @@ +# Google Stitch Prompt: Projects Overview + +## Purpose + +This prompt is for the next main-screen exploration of Themis in Google Stitch. + +It replaces the task-heavy dashboard as the preferred first impression. + +It should align with: + +- `05_ux-model.md` +- `07_visual-discovery.md` + +## Stitch Prompt + +Idea +A projects overview screen for Themis, a structured project and task management app for software engineers, technical leads, and solo builders who manage many projects at the same time. + +Theme +Calm operational notebook. Precise, modern, and technically mature. Neutral-first palette, restrained accents, strong typography, low visual noise, and minimal chrome. Avoid generic SaaS dashboard patterns, heavy KPI panels, crowded kanban layouts, colorful status overload, and enterprise control-room aesthetics. + +Content +Design one projects overview screen only. + +Include: +- a top page header with the Themis brand or workspace label, search, and one primary create action +- a short page heading that communicates this is the cross-project workspace +- a projects list or grid for multiple active projects +- each project block should show project name, concise summary, current status or momentum, task counts by state, one notable next step or blocker, and recent activity age +- each project block should include a clear path into the project without feeling like a dense dashboard card +- light filtering or sorting for status, owner, or recency +- a restrained secondary rail only if it adds calm cross-project context such as stale projects, major blockers, or recent decisions + +The screen should feel like: +- a clear entry point into multiple parallel workstreams +- a calm operational briefing +- a premium, structured product workspace + +The screen should not feel like: +- a task board +- a noisy analytics dashboard +- a grid of generic SaaS cards +- a PM admin console + +Layout guidance: +- prioritize projects over tasks +- give each project enough breathing room to feel important +- use typography and spacing before borders and filled cards +- keep the page easy to scan in under 10 seconds +- reduce secondary controls and avoid overcrowding the header + +## Short Stitch Prompt + +Idea +A projects overview screen for Themis. + +Content +Create one projects overview screen only for Themis. Show multiple active projects in a calm, structured layout with strong first-impression clarity. Include a top header, search, one primary create action, and a list or grid of project blocks. Each project should show its name, short summary, task counts by state, one important blocker or next step, and recent activity age. Keep the screen minimal, premium, and easy to scan. Avoid dense task dashboards, heavy analytics, and generic SaaS card grids. + +## Current Exploration + +### Screen + +![Projects Overview exploration](./assets/projects-overview.png) + +### Exported Assets + +- Screenshot: `./assets/projects-overview.png` +- HTML export: `./assets/projects-overview.html` +- Current Stitch screen: `Projects Overview (Utilitarian)` +- Current Stitch screen ID: `122fc46a33464f72a9391d72014a28b2` + +## Review + +The projects overview direction is now aligned for Themis. This utilitarian version is the right baseline for the product. + +### Approved Qualities + +- projects-first entry is still the right product decision +- clear orientation across multiple active projects +- project-level grouping is stronger than task-first entry +- the visual treatment is calmer and more believable +- repeated structure makes the page easier to scan +- the screen feels more useful than decorative + +### What To Preserve + +1. projects-first entry point +2. repeated project-block structure +3. restrained hierarchy and low visual noise +4. concise project summaries with operational signals +5. utilitarian tone over visual novelty + +### What To Watch In Future Iterations + +1. do not drift back into card variation or dashboard metrics +2. keep decorative ideas secondary to readability +3. preserve the utilitarian calm as more features are introduced + +### Documentation Status + +- status: approved baseline direction +- use this screen as the baseline for future project-level navigation and landing-page product previews diff --git a/docs/products/themis-task-system/12_backend-content-model.md b/docs/products/themis-task-system/12_backend-content-model.md new file mode 100644 index 0000000..66380bd --- /dev/null +++ b/docs/products/themis-task-system/12_backend-content-model.md @@ -0,0 +1,386 @@ +# Backend Content Model: Themis + +## Purpose + +This document defines the recommended backend content model for Themis. + +It answers a key product question: + +Should projects and tasks be stored as markdown files? + +## Short Answer + +Yes, but not as the only source of truth. + +Recommended direction: + +- use markdown for rich long-form task and project documentation +- use the application database for structured metadata, workflow state, relationships, permissions, and querying +- version the markdown content explicitly inside the product + +This gives Themis the strengths of documentation-first workflows without losing the operational capabilities of a real application. + +## Recommendation + +Themis should use a **hybrid model**. + +### Use Markdown For + +- project briefs +- task descriptions +- problem statements +- outcome definitions +- scope notes +- decisions +- update narratives +- agent-readable long-form context + +### Use The Database For + +- ids +- status +- priority +- owner +- labels +- relationships +- project membership +- timestamps +- filtering fields +- audit records +- permissions +- version metadata + +## Why Pure Markdown Files Are Not Enough + +Using plain markdown files alone sounds attractive, but it breaks down once Themis becomes a real multi-user product. + +Problems with markdown-only storage: + +1. querying by status, owner, blocker, or stale state becomes harder +2. concurrent edits become fragile +3. version history is available only if the system is tightly coupled to Git +4. cross-entity relationships become harder to enforce +5. permissions and audit trails become less reliable +6. product-level actions like `ready tasks`, `blocked tasks`, or `projects with stale updates` become less efficient + +Markdown-only would fit a personal knowledge base better than an operational product. + +## Why Markdown Still Matters + +Markdown is still a strong fit for Themis because the product is not only a workflow engine. + +It is also a structured documentation system. + +Markdown gives Themis: + +- durable, readable task definitions +- easy exportability +- strong human readability +- agent-friendly textual context +- future compatibility with repository-based workflows + +That makes markdown valuable as a **content format**, even if it is not the whole persistence strategy. + +## Recommended Canonical Model + +### Core Principle + +The database is the canonical operational source. + +Markdown is the canonical narrative format for long-form content fields. + +That means: + +- the product does not rely on filesystem files as its main store +- markdown content is stored and versioned in the database +- the UI renders and edits markdown content through structured fields + +## Entity Model + +### Project + +Suggested structured fields: + +- `id` +- `slug` +- `title` +- `summary` +- `status` +- `ownerId` +- `visibility` +- `labels` +- `createdAt` +- `updatedAt` +- `lastActivityAt` + +Suggested markdown-backed fields: + +- `briefMarkdown` +- `goalsMarkdown` +- `scopeMarkdown` +- `notesMarkdown` + +### Task + +Suggested structured fields: + +- `id` +- `projectId` +- `parentTaskId` optional +- `slug` +- `title` +- `summary` +- `status` +- `priority` +- `ownerId` +- `confidence` +- `blocked` +- `dueAt` optional +- `createdAt` +- `updatedAt` +- `lastActivityAt` + +Suggested markdown-backed fields: + +- `problemMarkdown` +- `expectedOutcomeMarkdown` +- `scopeInMarkdown` +- `scopeOutMarkdown` +- `implementationNotesMarkdown` + +### Task Requirement + +- `id` +- `taskId` +- `content` +- `order` +- `completed` optional + +### Acceptance Criterion + +- `id` +- `taskId` +- `content` +- `order` +- `completed` + +### Update Entry + +Structured fields: + +- `id` +- `taskId` +- `authorId` +- `authorType` (`human` or `agent`) +- `summary` +- `nextStep` +- `blocker` +- `createdAt` + +Markdown-backed field: + +- `detailsMarkdown` + +### Decision + +Structured fields: + +- `id` +- `taskId` +- `authorId` +- `createdAt` + +Markdown-backed fields: + +- `summaryMarkdown` +- `rationaleMarkdown` +- `consequenceMarkdown` + +## Versioning Model + +Versioning should be built into Themis itself, not left only to external Git history. + +### Recommendation + +Every markdown-backed field change should create a revision record. + +This allows: + +- restore previous versions +- compare revisions +- inspect who changed what +- keep agent edits visible and auditable + +## Revision Entities + +### Content Document + +Represents the current editable markdown document for a field or content block. + +Suggested fields: + +- `id` +- `entityType` (`project`, `task`, `update`, `decision`) +- `entityId` +- `fieldName` +- `currentRevisionId` +- `createdAt` +- `updatedAt` + +### Content Revision + +Represents a single historical version of markdown content. + +Suggested fields: + +- `id` +- `documentId` +- `revisionNumber` +- `markdown` +- `renderedText` optional cached plain text +- `changeSummary` +- `authorId` +- `authorType` (`human` or `agent`) +- `createdAt` + +## Versioning Rules + +1. every save to a markdown-backed field creates a new revision +2. the current entity points to the latest revision +3. the UI should allow viewing revision history on important fields +4. agent-created revisions must be clearly labeled +5. major changes should optionally require a change summary + +## Git Integration + +Git can still be useful, but it should be optional. + +### Good Uses Of Git + +- export projects or tasks as markdown files +- sync approved content to a repo +- archive important project documentation +- support developer-first workflows + +### What Git Should Not Be Responsible For + +- real-time application persistence +- permissions +- status transitions +- operational querying +- multi-user collaboration control + +So the correct posture is: + +- Themis owns the live data model +- Git can be a downstream export or sync target + +## API Shape + +Suggested endpoints: + +- `GET /api/projects` +- `POST /api/projects` +- `GET /api/projects/:id` +- `PATCH /api/projects/:id` +- `GET /api/tasks` +- `POST /api/tasks` +- `GET /api/tasks/:id` +- `PATCH /api/tasks/:id` +- `GET /api/content-documents/:id/revisions` +- `POST /api/content-documents/:id/revisions` +- `POST /api/content-documents/:id/restore/:revisionId` + +## Rendering Model + +The frontend should not treat markdown as loose blobs everywhere. + +Instead: + +- use structured fields in forms +- render markdown only where long-form context is appropriate +- keep list views driven by structured metadata, not markdown parsing + +That preserves speed and clarity in the UI. + +## Search Model + +Search should combine: + +- structured filters from the database +- full-text search across markdown-backed fields + +This allows queries like: + +- all blocked tasks in project X +- tasks mentioning `rate limiting` +- projects updated in the last 7 days +- tasks with missing scope definition + +## Agent Fit + +This hybrid model is strong for agents because it separates: + +- structured state for reliable automation +- markdown context for richer reasoning + +Agent-safe export shape should include both. + +Example: + +```json +{ + "id": "task_123", + "title": "Implement project revision history", + "status": "ready", + "priority": "high", + "project": { + "id": "project_themis", + "title": "Themis Core" + }, + "content": { + "problemMarkdown": "...", + "expectedOutcomeMarkdown": "...", + "scopeInMarkdown": "...", + "scopeOutMarkdown": "..." + }, + "requirements": ["save markdown revisions", "restore older revisions"], + "acceptanceCriteria": ["history is visible", "restore creates a new revision"], + "latestUpdate": { + "summary": "data model drafted", + "nextStep": "design revision endpoints" + } +} +``` + +## V1 Recommendation + +For V1, keep the model simple. + +Start with: + +1. PostgreSQL as the main store +2. markdown-backed long-form fields stored in normal tables +3. a `content_revisions` table for history +4. project-level and task-level revision history only +5. optional markdown export later + +Do not start with: + +- filesystem markdown as primary persistence +- Git as the main data source +- event sourcing +- overly granular versioning on every tiny field unless it is markdown-backed + +## Final Recommendation + +Themis should be **documentation-friendly**, not **filesystem-dependent**. + +Best approach: + +- database-first for operational state +- markdown-first for rich content fields +- built-in revision history for versioning +- optional Git export later + +That gives Themis the clarity of documents and the reliability of a real product backend. diff --git a/docs/products/themis-task-system/assets/landing-page-dark.html b/docs/products/themis-task-system/assets/landing-page-dark.html new file mode 100644 index 0000000..213df60 --- /dev/null +++ b/docs/products/themis-task-system/assets/landing-page-dark.html @@ -0,0 +1,316 @@ + + + + + +Themis | The Technical Manuscript + + + + + + + + +
+ +
+

+ Clarity for complex execution. +

+

+ Themis is a technical ledger designed for leads who manage multiple concurrent workstreams without the noise of generic project management tools. +

+
+ + +
+
+ +
+
+
+
+
+

Projects Overview

+

Operational briefing for active workstreams

+
+
+search +notifications +
+person +
+
+
+
+
+ +
+
+
+

Project Alpha

+

System-wide migration of the legacy auth modules.

+
+Active +
+
+
+
+
+
+Technical Distribution +12 Ready / 4 In Progress +
+
+
+ +
+
+
+

Infrastructure Core

+

Provisioning new GPU clusters in the Western Node.

+
+Stale +
+
+ Awaiting hardware allocation from Cluster 4 +
+
+
+
+
+
Major Blockers
+
+
+
+

Memory Leak: Neural Edge

+
+
+
+

API Latency Spike: Core

+
+
+
+
+
Recent Decisions
+
+

Approved Project Alpha schema transition.

+

Deprioritized Hardware Provisioning for Q4.

+
+
+
+
+
+
+
+ +
+
+
+
+

Projects, not chaos.

+

See every active project, current state, and next point of attention in one place.

+
+
+

Tasks with definition.

+

Keep scope, requirements, decisions, and next steps attached to the work itself.

+
+
+

Progress with signal.

+

Track what changed, what is blocked, and what comes next without status-noise overhead.

+
+
+
+
+ +
+
+
Execution
+

Task Detail: The center of gravity.

+

+ Most tools bury technical context in comments. Themis treats documentation, spec links, and status markers as first-class citizens in a focused, distraction-free view. +

+
+
+data_object +Scope and Requirements Definition +
+
+description +Direct Status and Decision Tracking +
+
+
+
+
+
+TASK-442 / OPS +
+
+In Progress +
+
+

API Rate Limiter Implementation

+

+ Implement token bucket algorithm for the edge gateway to prevent upstream saturation during peak traffic. +

+
+
+
+link +Technical Spec +
+v2.1 FINAL +
+
+
+verified +Security Review +
+Passed +
+
+
+ +
+
+
+ +
+
+
+

Engineered for teams who ship.

+
+
+
+

Focused on State

+

+ Generic tools prioritize social chatter. We prioritize technical state and execution velocity. No fluff, no distractions. +

+
+
+

Relational Ledger

+

+ While other tools break at scale, our ledger architecture maintains integrity and performance for complex dependency trees. +

+
+
+
+
+ +
+
+

Ready for structural clarity?

+

Join technical leads who prioritize execution over noise.

+
+ + +
+
+
+
+ + \ No newline at end of file diff --git a/docs/products/themis-task-system/assets/landing-page-dark.png b/docs/products/themis-task-system/assets/landing-page-dark.png new file mode 100644 index 0000000..08f8bb7 Binary files /dev/null and b/docs/products/themis-task-system/assets/landing-page-dark.png differ diff --git a/docs/products/themis-task-system/assets/landing-page.html b/docs/products/themis-task-system/assets/landing-page.html new file mode 100644 index 0000000..01ec412 --- /dev/null +++ b/docs/products/themis-task-system/assets/landing-page.html @@ -0,0 +1,312 @@ + + + + + +Themis | The Technical Manuscript + + + + + + + + + + +
+ +
+Engineering Command Center +

+ Clarity for complex execution. +

+

+ Themis is a technical ledger designed for leads who manage multiple concurrent workstreams without the noise of generic project management tools. +

+
+ + +
+
+ +
+
+
+
+
+
+

Active Infrastructure Ledger

+
+
+search +filter_list +
+
+
+ +
+
+
+

Project Delta

+

Distributed Node Migration

+
+84% COMPLETE +
+
+
+
+
+
+24 Tasks Pending +Deployment Window: Oct 12 +
+
+
+
+
+

Resource Allocation

+

Latency Overhead

+
+
12ms
+
+
+

Recent Activity

+
+
+
+

Merged PR #1290 into main

+
+
+
+

Architecture review completed by @jake

+
+
+
+
+
+

Stakeholder Velocity

+Q3 Comparison +
+
+
+
+
+
+
+
+
+
+
+
+
+
+ +
+
+
+filter_center_focus +

Signal over Noise

+

+ Automated filters suppress trivial notifications, surfacing only high-impact decisions and technical blockers that require lead intervention. +

+
+
+account_tree +

Structural Rigor

+

+ Built on a relational ledger architecture. Tasks aren't just rows; they are interconnected nodes with strict dependency tracking. +

+
+
+layers +

Operational Calm

+

+ A neutral, editorial interface designed to reduce cognitive load during 12-hour high-concurrency development cycles. +

+
+
+
+ +
+
+

Task Detail as the
Center of Gravity

+

+ Most tools bury technical context in comments. Themis treats documentation, spec links, and status markers as first-class citizens in a focused, distraction-free view. +

+
    +
  • +check_circle + Inline Technical Specification Rendering +
    • +
  • +check_circle + Direct Link to Version Control PRs +
    • +
  • +check_circle + Automated Completeness Checklists +
    • +
+
+
+
+
+TASK-442 / OPS +
+
+IN PROGRESS +
+
+

API Rate Limiter Implementation

+

+ Implement token bucket algorithm for the edge gateway to prevent upstream saturation during peak traffic. +

+
+
+Technical Spec +link +
+
+Security Review +verified +
+
+
+ +
+
+
+ +
+
+
+

Why the System is Different

+
+
+
+

Not a "Social" Tool

+

+ Generic tools prioritize "likes" and chatter. We prioritize technical state and execution velocity. No fluff, no distractions. +

+
+
+

Designed for Concurrency

+

+ While other tools break at 50+ tasks, our ledger architecture maintains performance and clarity at enterprise scale. +

+
+
+
+
+ +
+
+

Ready for structural clarity?

+ +

Current Waitlist: 12 Business Days

+
+
+
+ + + \ No newline at end of file diff --git a/docs/products/themis-task-system/assets/landing-page.png b/docs/products/themis-task-system/assets/landing-page.png new file mode 100644 index 0000000..4ce2795 Binary files /dev/null and b/docs/products/themis-task-system/assets/landing-page.png differ diff --git a/docs/products/themis-task-system/assets/projects-overview.html b/docs/products/themis-task-system/assets/projects-overview.html new file mode 100644 index 0000000..27d4ab1 --- /dev/null +++ b/docs/products/themis-task-system/assets/projects-overview.html @@ -0,0 +1,268 @@ + + + + + + + + + + + + + + +
+
+
+
+search + +
+
+
+ + +
+ +User profile +
+
+
+
+

Projects Overview

+

Active technical ledger for Q4 initiatives.

+
+
+
+
+
+
+

Core Infrastructure Migration

+Active +
+

Transitioning legacy databases to distributed cloud architecture with zero downtime requirements.

+
+42 Tasks +0 Blocked +Updated 45m ago +
+
+
+

Next Step

+

Finalize validation scripts for staging environment sync.

+
+
+
+
+
+
+
+

Security Audit Framework

+Blocked +
+

Automated compliance mapping for international data protection standards across all microservices.

+
+18 Tasks +3 Blocked +Updated 2h ago +
+
+
+

Primary Blocker

+

Awaiting legal clearance for third-party scanning tool integration.

+
+
+
+
+
+
+
+

DevOps Pipeline Refactor

+Stale +
+

Optimizing CI/CD build times by implementing advanced caching and parallel test execution.

+
+12 Tasks +0 Blocked +Updated 5d ago +
+
+
+

Next Step

+

Assign secondary reviewer for pipeline-as-code definitions.

+
+
+
+
+
+
+
+

API Documentation Engine

+Active +
+

Generating real-time interactive developer documentation from live OpenAPI specifications.

+
+31 Tasks +0 Blocked +Updated 1h ago +
+
+
+

Next Step

+

Integrate with authentication middleware for private endpoints.

+
+
+
+
+
+
+
+

Frontend Component Library

+Active +
+

Standardizing UI patterns across internal tools using a centralized, theme-able CSS framework.

+
+54 Tasks +0 Blocked +Updated 15m ago +
+
+
+

Next Step

+

Export final design system tokens for mobile engineering team.

+
+
+
+
+
+ +
+
+
+ \ No newline at end of file diff --git a/docs/products/themis-task-system/assets/projects-overview.png b/docs/products/themis-task-system/assets/projects-overview.png new file mode 100644 index 0000000..cacf3a7 Binary files /dev/null and b/docs/products/themis-task-system/assets/projects-overview.png differ diff --git a/docs/products/themis-task-system/assets/themis-sign-in.html b/docs/products/themis-task-system/assets/themis-sign-in.html new file mode 100644 index 0000000..2b456a4 --- /dev/null +++ b/docs/products/themis-task-system/assets/themis-sign-in.html @@ -0,0 +1,164 @@ + + + + + +Themis - Sign In + + + + + + + + + + + + + +
+

+ Themis +

+
+ +
+
+

Sign in

+

+ Enter your details to access your workspace. +

+
+ +
+ +
+ +
+ +
+
+ +
+ +
+ + +
+
+ +
+ + + Forgot Password? + +
+ + +
+ + +
+ \ No newline at end of file diff --git a/docs/products/themis-task-system/assets/themis-sign-in.png b/docs/products/themis-task-system/assets/themis-sign-in.png new file mode 100644 index 0000000..e1c0036 Binary files /dev/null and b/docs/products/themis-task-system/assets/themis-sign-in.png differ