MrSphay/intelligence-terminal
1
0
Fork 0
Code Issues 10 Pull Requests Actions Packages Projects Releases Wiki Activity

[Feature] Operator Profiles for Briefing Style, Alert Routing, and Dashboard Focus #31

New Issue
Open
opened 2026-05-17 12:26:26 +00:00 by MrSphay · 0 comments
MrSphay commented 2026-05-17 12:26:26 +00:00
Owner
Copy Link

Summary

Add operator profiles that tailor Crucix to different use cases such as home-server monitoring, global macro trading, OSINT research, maritime risk, cyber watch, or disaster response.

Why This Matters

A single default dashboard and briefing style cannot serve every operator well. Profiles make the same data engine feel purpose-built without forking the product.

Scope

  • Bug fix: No
  • New source: No
  • Dashboard/UI change: Yes
  • LLM/provider change: Prompt/context selection
  • Other: Product configuration layer

Proposed Behavior

  • Provide built-in profiles with source emphasis, alert thresholds, briefing verbosity, dashboard default layers, and delivery routing preferences.
  • Allow one active profile through env/config, with optional dashboard switching for local trusted deployments.
  • Briefing generation uses the active profile to prioritize sections and language, while still preserving Source Integrity.
  • Alerts can route differently by profile, for example cyber alerts to Discord and macro alerts to Telegram.

Acceptance Criteria

  • Profiles are declarative config, not code branches.
  • Default behavior remains unchanged when no profile is selected.
  • At least 4 built-in profiles are documented: Home Server, Macro Trader, OSINT Analyst, Crisis Monitor.
  • Tests cover profile loading, default fallback, briefing option mapping, and alert routing selection.
  • Dashboard clearly shows the active profile when profiles are enabled.

Maintenance Impact

Adds product surface but should reduce operator-specific config sprawl. Must avoid embedding financial advice promises into profiles.

Additional Context

This complements the existing LLM provider abstraction and BRIEF_VERBOSITY setting.

## Summary Add operator profiles that tailor Crucix to different use cases such as home-server monitoring, global macro trading, OSINT research, maritime risk, cyber watch, or disaster response. ## Why This Matters A single default dashboard and briefing style cannot serve every operator well. Profiles make the same data engine feel purpose-built without forking the product. ## Scope - Bug fix: No - New source: No - Dashboard/UI change: Yes - LLM/provider change: Prompt/context selection - Other: Product configuration layer ## Proposed Behavior - Provide built-in profiles with source emphasis, alert thresholds, briefing verbosity, dashboard default layers, and delivery routing preferences. - Allow one active profile through env/config, with optional dashboard switching for local trusted deployments. - Briefing generation uses the active profile to prioritize sections and language, while still preserving Source Integrity. - Alerts can route differently by profile, for example cyber alerts to Discord and macro alerts to Telegram. ## Acceptance Criteria - Profiles are declarative config, not code branches. - Default behavior remains unchanged when no profile is selected. - At least 4 built-in profiles are documented: Home Server, Macro Trader, OSINT Analyst, Crisis Monitor. - Tests cover profile loading, default fallback, briefing option mapping, and alert routing selection. - Dashboard clearly shows the active profile when profiles are enabled. ## Maintenance Impact Adds product surface but should reduce operator-specific config sprawl. Must avoid embedding financial advice promises into profiles. ## Additional Context This complements the existing LLM provider abstraction and `BRIEF_VERBOSITY` setting.
MrSphay added the enhancementresearchproduct labels 2026-05-17 12:26:26 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
design-revert
Reverts visual/design changes
 enhancement
New feature or product improvement
 frontend-redesign
Frontend redesign and app-shell/UI work
 marketing-finalization
Product presentation, README, packaging metadata, and customer-facing communication.
 product
User-facing product capability or workflow
 research
Research-originated product idea ready for implementation design
No Label enhancement product research
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
MrSphay
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: MrSphay/intelligence-terminal#31
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?