AICHE +CCapacities Integration
Voice input for object-based notes
Speak your knowledge structures into Capacities. Define objects naturally.
The short answer: open Capacities, click into any note or object, press ⌃+⌥+R (Mac) or Ctrl+Alt+R (Windows/Linux), speak your object schema or content for 60-120 seconds, and AICHE inserts structured specifications.
Capacities' object-based system requires defining types, properties, and relationships that take 12+ minutes to type per object type. You envision the complete data structure with collections and templates, but typing slows implementation.
- Open Capacities in your browser or desktop app.
- Navigate to your space or create a new object.
- Click where you want to add content or define structure.
- Press your AICHE hotkey to start recording.
- Speak your complete object definition or note content.
- Press the hotkey again-AICHE transcribes, applies Content Organization to format schemas, and inserts the text.
Object Type Design
Defining Types and Properties
Before building object types, dictate the complete structure. Example: "Create an object type called Meeting with properties for meeting title as text field, date and time as datetime picker, attendees as collection of people objects, agenda items as list property allowing multiple text entries, key decisions as long text area with rich formatting, action items as collection linked to Task objects with bidirectional reference, meeting notes as long text, and recording link as URL field. Set default view to show title, date, and attendees. Configure page template to include agenda and decisions sections automatically."
The spoken schema guides manual implementation in Capacities' object editor. You build the properties using the transcript as reference.
Linked Object Relationships
For connected object types, speak the relationships explicitly: "Create a Task object type with title as text, description as long text, status as select with options Not Started, In Progress, Blocked, and Completed, assignee as person from team directory, due date as date field, priority as select with High, Medium, and Low, estimated hours as number, and related meeting as collection linking back to Meeting objects. When a task is created from a meeting, the bidirectional link automatically appears in both objects. Add a property to Task for parent project as reference to Project object type."
AICHE captures the complete relationship logic including bidirectional links and cascading references.
Daily Notes and Templates
Structured Daily Capture
Capacities' daily notes use templates with predefined structure. Dictate template specifications: "Set up daily note template with sections for Morning Planning, Time Blocking, Meeting Notes, and Evening Reflection. Morning Planning section includes a collection reference to high priority tasks due today pulled from Task objects where due date equals today and status not equals Completed. Time Blocking section uses a table with columns for time, activity, and actual versus planned comparison. Meeting Notes section creates new Meeting objects inline with quick capture template. Evening Reflection section uses long text for free-form journaling with prompts for wins, challenges, and tomorrow's focus."
Voice removes the tedium of configuring template structure while preserving the complete specification.
Project Planning Objects
For complex project objects, speak the full structure: "Create Project object type with project name, description, status select, start and end dates, project lead as person, team members as collection of people, budget as number with currency, actual spend as number, milestones as collection of Milestone objects, tasks as collection linking Task objects filtered to show incomplete items first, related meetings as collection of Meeting objects, project documentation as file attachments, and notes as long text. Add calculated property showing completion percentage by counting completed tasks divided by total tasks. Include another calculated property for budget variance showing difference between budget and actual spend with color coding for over or under budget."
The verbal object definition translates to Capacities' object editor during manual setup, clarifying all properties and calculations.
Knowledge Organization
Research Object Networks
When building research structures, dictate the object network: "Create Research Note object type for literature review. Properties include source title, author, publication date, URL, key arguments as list, my reactions as long text, related topics as tags, connected notes as collection of other Research Note objects, and action items as collection of Task objects for follow-up research. Create separate object type for Concept with concept name, definition, examples, related research notes as collection, related projects as collection showing where this concept applies, and synthesis as long text explaining connections across sources."
The spoken network structure becomes implementation guidance for building your research system in Capacities.
Meeting to Action Workflow
For structured workflows connecting objects, speak the process: "During team meeting, create Meeting object with attendees and agenda. While discussing, add key decisions inline using voice by dictating each decision point with context and rationale. When action items emerge, create Task objects directly from meeting notes with automatic linking. Assign each task to person, set due date, and mark priority. After meeting, the Meeting object shows all linked tasks with status. Team members see their assigned tasks in their person object with bidirectional references back to the originating meeting. Weekly review pulls all incomplete tasks from meetings in the past week using collection query."
AICHE captures the complete workflow specification showing how objects connect through the process.
Result: object type definitions with complex properties, collections, and calculated fields that took 20 minutes to type while switching between planning and implementation now take 6 minutes to dictate, and the spoken specifications document your knowledge system structure for onboarding and refinement.
Do this now: open Capacities, press your hotkey, and dictate one complete object type with properties, collections, calculated fields, and connections to other object types. Build the structure using your transcript as the blueprint.