# Kortex Hub & Tana for Kortex: A Comprehensive Workflow Guide

**Version:** 1.0 (Based on May 5th Discussion & Provided PDF)

## I. Introduction: The Content Creator's Challenge & Solution

Content creators juggle ideation, research, drafting, editing, publishing, and managing the tasks associated with each stage. This demands a robust yet flexible system. This guide details a workflow optimized for your needs, establishing **Kortex** as the primary **"Kortex Hub"** for capture, ideation, research synthesis (leveraging Readwise & kAI), and content development. **Tana** serves as the essential **"Tana for Kortex"** support system, managing projects, tasks (derived from Kortex activities), scheduling, and structured reviews across your key areas (Pilocon, Home, Infor), grounded in Getting Things Done (GTD) principles.

**Core Principles:**

*   **Kortex Hub:** Central command for capture, synthesis, writing.
*   **Tana Support:** Trusted agent for GTD task/project management, scheduling, reviews.
*   **Simplicity & Flow:** Minimize friction between tools.
*   **Reflective Practice:** Integrate Tana-based reviews (Daily, Weekly, Quarterly).
*   **Shareability:** Logical structure for potential future sharing.
*   **Integration:** Leverage Kortex (Readwise/kAI) and Tana (API/Calendar Sync).

This approach uses Kortex's strengths in AI-powered knowledge work and writing, supported by Tana's powerful structuring and task management capabilities.

## II. Kortex Hub: Capture, Synthesis & Writing

Kortex is your primary environment for interacting with ideas and producing content.

**A. Kortex Core Concepts:**

*   **Writing Experience:** Minimalist interface for focused writing, reducing clutter while keeping related ideas accessible.
*   **Capture:** Prioritize direct capture into Kortex (global hotkey `Option/Alt+C`, mobile input, web clips, highlights).
*   **Documents & Elements:** Use Documents for long-form content and Elements for reusable templates/blocks.
*   **Connections & Tags:** Organize non-hierarchically using links and tags.
*   **Library:** Central repository for PDFs, web links, video transcripts, and Readwise highlights. Kortex can transcribe various sources.
*   **kAI (Kortex AI):** Integrated AI for summarizing, answering questions (using workspace/document context), generating ideas/outlines, and assisting writing. Chat directly with PDFs, YouTube videos, and Readwise highlights. Utilize prebuilt AI workflows.

**B. Setting up Kortex Hub:**

1.  **Workspace Structure:** Keep it simple initially. Create Documents for active `#ContentPiece` items. Use folders/tags mirroring Tana Areas (Pilocon, Home, Infor) if helpful, but rely primarily on search and connections.
2.  **Capture Habit:** Make direct Kortex capture your default (global hotkey, mobile). Capture research materials (articles, PDFs, videos) directly into the Kortex Library.
3.  **Readwise Integration:** Ensure Readwise is connected and syncing highlights to your Kortex Library.
4.  **Library Use:** Actively use the Library. Upload key research PDFs. Link Library items to relevant Documents as you write.
5.  **Writing Environment:** Utilize the multi-pane view to reference outlines, captures, or library items while writing in the main Document pane.
6.  **Strategic kAI Use:**
    *   *Synthesis:* Ask kAI to connect new captures with existing notes/highlights/writing.
    *   *Research:* Query kAI across your library (PDFs, videos, Readwise) for quick insights or summaries.
    *   *Ideation/Outlining:* Use kAI to brainstorm, generate titles, or create initial outlines from notes/sources.
    *   *Drafting:* Use AI workflows as a *starting point*, always heavily editing for your voice. Use kAI to overcome writer's block.
    *   *Editing:* Leverage AI for grammar, clarity, and suggestions.
7.  **Templates (Elements):** Create Kortex Elements for recurring content structures (e.g., Newsletter sections, Pilocon reflection prompts).

**C. Kortex Considerations:**

*   **Pricing:** Be mindful of AI usage and storage limits based on your plan (Free, Kore, Premium).
*   **Development:** Kortex is evolving; some features might be newer or still maturing.
*   **Privacy:** Review the privacy policy regarding data handling, especially with AI features involving third-party providers.

## III. Tana for Kortex: GTD Support System

Tana provides the structure, oversight, scheduling, and reflective practice for your Kortex-driven work.

**A. Understanding Tana's Building Blocks (GTD Context):**

*   **Nodes:** Flexible bullet points forming a knowledge graph.
*   **Supertags:** Templates (#Task, #Project) defining structured information.
*   **Fields:** Specific data points within supertags (Status, Due Date, Kortex Link).
*   **Live Searches & Views:** Dynamic dashboards (Lists, Tables, Cards, Calendar) that automatically update.

**B. Implementing GTD in Tana (Supporting Kortex):**

1.  **Capture (Minimal in Tana):** Primarily capture *tasks* derived from Kortex or non-content items (meetings, calls) in Tana's Daily Note or via Quick Add. If a content idea *must* be captured in Tana, create an `#idea` node and an immediate `#task` to "Transfer Idea to Kortex".
2.  **Clarify & Organize (Tana's Core Role):**
    *   **Processing:** Regularly process items captured in Tana (e.g., from Daily Note). Ask: Is it actionable?
    *   **Supertags for Structure:** Define core supertags:
        *   `#area`: High-level areas. Key Fields: `Name` (Pilocon, Home, Infor).
        *   `#project`: Multi-step outcomes within an Area. Key Fields: `Status` (Planning, Active, On Hold, Completed), `Goal`, `Deadline` (optional), `Area Link` (Instance: #area), `Kortex Project Link` (URL, optional), `Tasks` (Search: Find #Task where Related Project is PARENT), `Related Content Pieces` (Search: Find #ContentPiece where Related Project is PARENT).
        *   `#task`: Specific, actionable steps, *often derived from Kortex*. Key Fields: `Status` (Next Action, Doing, Waiting For, Completed, Someday/Maybe - *No Inbox status needed if tasks are defined directly*), `Due Date`, `Priority` (Optional: P1-P3), `Context` (@Writing, @Computer, @Calls, etc.), `Related Project` (Instance: #project), `Related Content Piece` (Instance: #ContentPiece), **`Kortex Link` (URL - CRUCIAL link back to the Kortex doc/section)**. Configure checkbox mapping (Checked=Completed, Unchecked=Next Action).
        *   `#ContentPiece`: Represents specific outputs (article, newsletter). Primarily managed via tasks, but useful for grouping. Key Fields: `Status` (Idea, Outlining, Drafting, Editing, Published, etc. - *managed via linked Tasks*), `Publish Date`, `Format`, `Related Project` (Instance: #project), `Kortex Link` (URL), `Link to Published URL`.
        *   `#dailylog`: Daily reflection. Key Fields: `Date`, `Tasks Completed` (Search: Find #Task completed today), `Points to Ponder` (Text), `Gratitude/Wins` (Text).
        *   `#weeklyreview`: Structured review. Key Fields: `Date`, `Review Checklist` (Template Node/Text).
        *   `#quarterlyreview`: Deeper reflection. Key Fields: `Date`, `Retreat Notes`, `Goal Progress`, `Next Quarter Priorities`, `Action Items` (Search: Find #Task/#Project created during review).
    *   **Organizing Tasks:** Assign `Status` (Next Action, etc.), `Context`, `Due Date`, and link to `#project`/`#ContentPiece`. Crucially, add the `Kortex Link` URL.
3.  **Reflect (Tana):** The cornerstone of maintaining trust in your system.
    *   **Daily Review (`#dailylog`):** End-of-day reflection on tasks completed, ponder points.
    *   **Weekly Review (`#weeklyreview`):** Use a Tana dashboard with searches based on the GTD checklist:
        *   *Get Clear:* Capture open loops. Process any remaining Tana captures.
        *   *Get Current:* Review `Next Action` list; review Calendar (Tana view or Google Sync); review `Waiting For` list; review Active `#project` list (ensure next actions exist); review relevant checklists.
        *   *Get Creative:* Review `Someday/Maybe` list; brainstorm new ideas (capture in Kortex!).
    *   **Quarterly Review (`#quarterlyreview`):** Deeper review during retreats using a dedicated Tana dashboard.
4.  **Engage (Tana):** Decide what to work on based on Tana views (`Next Actions @Context`, `Tasks Due Today`).
5.  **Execute (Kortex/Other):** Perform the task, primarily writing/developing in Kortex, referencing the Tana task list.

**C. Essential Tana Views/Dashboards (Supporting Kortex):**

*   **`ACTIONS TODAY`:** Search: `#task` WHERE (`Due Date` is Today OR `Priority` is P1) AND `Status` is NOT Completed.
*   **`NEXT ACTIONS by Context`:** Search: `#task` WHERE `Status` is Next Action. View: List, Grouped by `Context`.
*   **`PROJECTS OVERVIEW`:** Search: `#project` WHERE `Status` is Active. View: Cards/Table showing Status, Goal, Deadline, `Kortex Project Link`.
*   **`WAITING FOR`:** Search: `#task` WHERE `Status` is Waiting For.
*   **`CONTENT PIECES (by Status)`:** Search: `#ContentPiece`. View: Cards, Grouped by `Status` (useful overview, but tasks drive the state).
*   **`DAILY LOGS`:** Search: `#dailylog`. View: Calendar or List.
*   **`WEEKLY REVIEW Dashboard`:** Node containing searches for each review step (Clear, Current, Creative). View: Tabs or structured List.
*   **`QUARTERLY REVIEW Dashboard`:** Similar structure for deeper review.

**D. Tana Integrations & Automation:**

*   **Google Calendar Sync:** Enable in Settings to see Tana task deadlines on your calendar.
*   **Tana API/Commands:** Focus on supporting Kortex:
    *   Commands to quickly create Tana `#task` nodes (potentially pre-filled) triggered manually when a Kortex stage needs action.
    *   Commands to automate review setup (e.g., populate `#weeklyreview` with completed tasks).

## IV. The Integrated Workflow: Kortex Hub + Tana Support

1.  **Capture & Ideation (Kortex):** Default capture location. Use kAI + Readwise for synthesis.
2.  **Research (Kortex):** Leverage kAI and integrated Library.
3.  **Development & Outlining (Kortex):** Structure content within Kortex.
4.  **Define Actionable Steps (Kortex -> Tana):** As Kortex work progresses, identify next actions. Go to Tana, create specific `#task` nodes (e.g., 

"Draft Section A", "Publish Newsletter"). Assign `Status`, `Context`, `Due Date`. **Crucially, copy the Kortex document/section URL and paste it into the `Kortex Link` field of the Tana `#task`.**
5.  **Drafting & Writing (Kortex):** Perform the main writing work in Kortex, using its focused environment. Refer to Tana for the list of actionable tasks.
6.  **Editing (Kortex):** Edit within Kortex, using kAI as needed.
7.  **Content Repurposing (Kortex):** Adapt content into different formats within Kortex.
8.  **Define Publishing Tasks (Kortex -> Tana):** Create new `#task` nodes in Tana for publishing each piece, linking back to the Kortex source via the `Kortex Link` field.
9.  **Scheduling & Publishing (Tana & External):** Use Tana tasks + Google Calendar sync for deadlines. Publish via external platforms.
10. **Update Tana:** Mark corresponding `#task` nodes in Tana as `Done`.
11. **Reviews (Tana):** Conduct Daily, Weekly, and Quarterly reviews in Tana using the dedicated dashboards.

## V. Step-by-Step Implementation

**(Refer to PDF / Previous Guide Sections for detailed Tana Supertag/Field/Search configuration steps if needed - focusing here on the Kortex-centric adjustments)**

1.  **Kortex Setup:**
    *   Prioritize: Connect Readwise. Organize workspace simply (Folders/Tags for Areas: Pilocon, Home, Infor). Practice direct capture (hotkey, mobile). Experiment heavily with kAI + Library for synthesis and drafting.
2.  **Tana Setup (Focus on Support):**
    *   Review/Simplify Supertags: Ensure `#area`, `#project`, `#task`, `#ContentPiece`, `#dailylog`, `#weeklyreview`, `#quarterlyreview` exist.
    *   **Crucial Field:** Add/Confirm the `Kortex Link` (URL type) field exists on `#task` and `#ContentPiece` supertags.
    *   Refine Task Status: Remove `Inbox` status from `#task` if tasks are always defined deliberately from Kortex work. Default `Unchecked` checkbox to `Next Action`.
    *   Build/Refine Views: Focus Tana dashboards on task oversight (`ACTIONS TODAY`, `NEXT ACTIONS by Context`), project status (`PROJECTS OVERVIEW`), and reviews (`WEEKLY/QUARTERLY REVIEW`).
    *   Integrations: Set up Google Calendar Sync.
3.  **Practice the Workflow:**
    *   **Capture -> Kortex.**
    *   **Synthesize/Develop -> Kortex.**
    *   **Identify Action -> Create Task in Tana + Add Kortex Link.**
    *   **Manage/Schedule Tasks -> Tana.**
    *   **Execute Writing Task -> Kortex (referencing Tana task list).**
    *   **Review -> Tana.**
    *   Refine based on friction points.

## VI. Website Content Outline (workflow.pilocon.com)

**(Goal: Simple, clear explanation of the workflow, visually aligned with pilocon.com)**

*   **Homepage:**
    *   Headline: Streamlining Content Creation: The Kortex Hub & Tana Support System
    *   Intro: Briefly explain the challenge for creators and introduce the Kortex + Tana solution tailored for Pilocon's reflective content style.
    *   Visual: Workflow Diagram (Simplified version if needed).
    *   Core Principles: Kortex for Capture/Writing, Tana for Tasks/Reviews.
    *   Navigation: Workflow Steps, Tool Setup, Printable Guide.
*   **Workflow Steps Page:**
    *   Detailed breakdown of the 11 steps from Section IV (Capture -> Review).
    *   Use clear headings and concise descriptions.
    *   Embed simplified diagram sections if helpful.
*   **Tool Setup Page:**
    *   **Kortex Hub Setup:** Key configuration points (Capture, Readwise, kAI use, Organization).
    *   **Tana Support Setup:** Key configuration points (Core Supertags - focus on `#task` with `Kortex Link`, `#project`, `#area`, Review tags; Key Dashboards).
    *   Emphasis on the manual linking step.
*   **Printable Guide Page:**
    *   Link to download the full comprehensive guide (this document, formatted for print/PDF).
*   **(Optional) About/Philosophy Page:** Briefly explain *why* this workflow fits the Pilocon values (intentionality, reflection, managing complexity).
*   **Visual Style:** Use colors, fonts, and layout consistent with pilocon.com (likely clean, professional, perhaps blues/whites/grays based on current site). Use sailing/navigation metaphors where appropriate, aligning with the Pilocon brand.

## VII. Conclusion: Building Your Flow State

This refined workflow places Kortex at the heart of your creative process, leveraging its AI and synthesis capabilities, while Tana provides the essential structure for managing commitments and facilitating reflection. By starting simple, focusing on the crucial Kortex -> Tana linking step, and consistently using the review processes in Tana, you can build a powerful, personalized system. This structure aims to free your mental energy from managing the *process* to focusing on the *creation* and *reflection* central to Pilocon's mission, helping you achieve a state of productive flow.