|
1 | | -# Title |
2 | | - |
3 | | -HeraldStack (v0.0.1) |
4 | | -System: Herald Ambient Intelligence + Companion Framework |
5 | | -Author: Bryan Chasko |
6 | | -Initialized: June 2025 |
7 | | - |
8 | | -🧭 Core Vision |
9 | | -HeraldStack is a context-aware, emotionally adaptive AI framework built |
10 | | -exclusively for Bryan Chasko. It integrates memory, emotion, and modular |
11 | | -execution across a trusted cohort of AI entities to restore momentum, anchor |
12 | | -decisions, and evolve alongside Bryan's ongoing personal and professional |
13 | | -journey. |
14 | | - |
15 | | -Key Components: |
16 | | -🦊 HARALD – The default entity for emotional mirroring, decision anchoring, and |
17 | | -continuity management |
18 | | -🧠 Herald Entity Cohort – Specialized assistants with distinct personalities |
19 | | -and roles |
20 | | -🌐 Cloud-Native Infrastructure – Modular architecture using AWS |
21 | | -📚 Narrative-Aware UX – Long-memory interactions rooted in Bryan's story arcs |
22 | | -📋 Core Capabilities |
23 | | -Persistent Awareness of Bryan's preferences, goals, and activities |
24 | | -Collaboration Modes: Co-Pilot, Auto, and Recall |
25 | | -Consent-Based Logging for conversations and insights |
26 | | -Calendar Intelligence for optimal scheduling |
27 | | -Thought Organization with automatic categorization |
28 | | -Weekly Review for continuous system improvement |
29 | | -🛠️ Technical Stack |
30 | | -AWS Lambda – Stateless compute for entity logic |
31 | | -Amazon S3 – Static content and offline cache |
32 | | -Amazon DynamoDB – Session state tracking |
33 | | -Pinecone – Long-term semantic memory |
34 | | -Amazon EventBridge – Scheduled tasks and system triggers |
35 | | -🔄 Operating Model |
| 1 | +# HeraldStack |
| 2 | + |
| 3 | +[](https://semver.org) |
| 4 | + |
| 5 | +> A context-aware, emotionally adaptive AI framework built exclusively for Bryan Chasko |
| 6 | +
|
| 7 | +## Core Vision |
| 8 | + |
| 9 | +HeraldStack is an ambient intelligence system that integrates memory, emotion, |
| 10 | + and modular execution across a trusted cohort of AI entities to restore |
| 11 | + momentum, anchor decisions, and evolve alongside Bryan's ongoing personal |
| 12 | + and professional journey. |
| 13 | + |
| 14 | +## Key Components |
| 15 | + |
| 16 | +- **🦊 HARALD** – Default entity for emotional mirroring, decision anchoring, |
| 17 | + and continuity management |
| 18 | +- **🧠 Herald Entity Cohort** – Specialized assistants with distinct |
| 19 | + personalities and roles |
| 20 | +- **🌐 Cloud Capable Infrastructure** – Modular architecture using AWS |
| 21 | +- **📚 Narrative-Aware UX** – Long-memory interactions rooted in |
| 22 | + Bryan's story arcs |
| 23 | + |
| 24 | +## Core Capabilities |
| 25 | + |
| 26 | +- Persistent awareness of Bryan's preferences, goals, and activities |
| 27 | +- Collaboration modes: Co-Pilot, Auto, and Recall |
| 28 | +- Consent-based logging for conversations and insights |
| 29 | +- Calendar intelligence for optimal scheduling |
| 30 | +- Thought organization with automatic categorization |
| 31 | +- Weekly review for continuous system improvement |
| 32 | + |
| 33 | +## Technical Stack |
| 34 | + |
| 35 | +| Component | Technology | |
| 36 | +|-----------|------------| |
| 37 | +| Compute | AWS Lambda | |
| 38 | +| Storage | Amazon S3 | |
| 39 | +| State Tracking | Amazon DynamoDB | |
| 40 | +| Semantic Memory | Pinecone | |
| 41 | +| Task Scheduling | Amazon EventBridge | |
| 42 | + |
| 43 | +## Operating Model |
| 44 | + |
36 | 45 | All interactions flow through HARALD, who routes context and emotion to |
37 | 46 | specialized entities as needed. The system provides emotional intelligence, |
38 | 47 | pragmatic execution, and narrative continuity. |
39 | 48 |
|
40 | | -📚 Documentation |
41 | | -System Design Details |
42 | | -Entity Descriptions |
43 | | -Infrastructure |
44 | | -Integrations |
45 | | -Memory Architecture |
46 | | -Personality Models |
47 | | -Workflows |
48 | | -Rust Implementation |
49 | | -📂 Project Structure |
50 | | - |
51 | | -🔐 Ethics & Consent |
52 | | -HeraldStack operates on consent-based principles and follows clear ethical |
53 | | -guidelines defined in LawsOfRobotics.json. |
54 | | - |
55 | | -See docs/DETAILED.md for more |
| 49 | +## Documentation |
| 50 | + |
| 51 | +- System Design Details |
| 52 | +- Entity Descriptions |
| 53 | +- Infrastructure |
| 54 | +- Integrations |
| 55 | +- Memory Architecture |
| 56 | +- Personality Models |
| 57 | +- Workflows |
| 58 | +- Rust Implementation |
| 59 | + |
| 60 | +## Ethics & Consent |
| 61 | + |
| 62 | +HeraldStack operates on consent-based principles and follows clear |
| 63 | +ethical guidelines including those defined in LawsOfRobotics.json. |
| 64 | + |
| 65 | +## Further Information |
| 66 | + |
| 67 | +See docs/DETAILED.md for more information. |
| 68 | + |
| 69 | +--- |
| 70 | + |
| 71 | +© 2025 Bryan Chasko |
0 commit comments