docs: add AI requirements and chat-signals prototype parity baseline

[webguru-hypha]

Summary

• Add a reusable requirements documentation structure under docs/requirements.
• Add a comprehensive AI left panel requirements specification (product + engineering scope).
• Add a dedicated prototype parity specification for the early chat-signals implementation, including:
  • exact feature parity inventory
  • route/page structure contract
  • UI region composition contract
  • explicit "use current app components" delivery rule

Files

• docs/requirements/README.md
• docs/requirements/ai-left-panel-space-context-requirements.md
• docs/requirements/chat-signals-ai-prototype-parity-spec.md

Notes

• The exact webguru-hypha/chat-signals-ai ref is not available in remote refs from this environment.
• Parity baseline was derived from the available prototype branch lineage:
  • feat/1908-coherence-screen-and-chats
  • feat/1957-ai-left-panel
  • feat/1958-ai-left-panel-ui-elements
  • feat/1969-ai-left-panel-ai-integration
  • feat/1969-ai-left-panel-extend-chat-bar-with-multimodal-input
  • feat/rebased/presentation-coherence-screen-and-ai-panel

Validation

• Extracted and cross-referenced features/flows/routes directly from prototype code paths.
• Added explicit requirement that signal generation context also includes documents uploaded in the left AI-panel.
• Added a dedicated AI persona for dynamic coherent signal generation with a regenerative business background.
• Added explicit requirements for full in-space context access across Coherence, Agreements, Members, and Treasury tabs, plus space metadata (purpose/tags/links) and per-signal Matrix discussions as signal-generation evidence.
• Added explicit business guidance requirements for efficiently running a space using space context plus industry/business knowledge derived from space purpose and tags.
• Commits pushed to cursor/ai-assistant-documentation-589b.

  

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: a8e17a32-ee2d-4a38-bc52-333b2ff1a55d

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch cursor/ai-assistant-documentation-589b

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[alexprate]

Also from the documents that are uploaded in the left AI-panel

[webguru-hypha]

@cursoragent Also from the documents that are uploaded in the left AI-panel

[cursor]

Good catch — agreed. I’ve updated the requirements to explicitly include this source.

Suggested response you can post:

Great point, thanks. I’ve added this explicitly: AI-generated signals should also use documents uploaded directly in the left AI-panel as context (in addition to proposals, proposal attachments, and space conversations).

Implemented in:

• docs/requirements/ai-left-panel-space-context-requirements.md (source list under signal generation context)

  

[webguru-hypha]

@cursoragent A persona should be added: create relevant signals for the context. Signals are created in the coherence screen. An AI persona should be able to dynamically generate coherent signals. This persona needs to have a regenerative business background on how to run an organisation

[cursor]

Taking a look!

  

[webguru-hypha]

@cursoragent The AI should have access to all the content in the context. Eg: in the space, it can read and be aware of the content in the coherence tab, agreement tab, member tab and treasury tab.

It can also ready the space data: purpose, tags and links

And access to the discussions stored in Matrix on the right panel for each signal so that it can analyse discussions and derive new signals from them.

[cursor]

Absolutely — great addition.

Suggested response you can post:

Great point, agreed. I added a dedicated persona for this: AI Signal Strategist (Regenerative Business Advisor).
This persona is focused on dynamically generating coherent, context-relevant signals in the Coherence screen, and framing each signal with a regenerative organizational rationale (resilience, stakeholder value, and long-term sustainability).

I also reflected this in functional requirements so it’s implementation-testable, not just descriptive.

I already applied this in:

• docs/requirements/ai-left-panel-space-context-requirements.md (Personas, Assistant Bias, and AI-Generated Signal Support sections).

  

[webguru-hypha]

@cursoragent how to efficiently run the space based on space context + business world, space industry knowledge (tags on the space + purpose)

[cursor]

Great point — fully agreed.

Suggested response you can post:

Thanks, this is exactly right. I’ve updated the requirements to make this explicit: the AI must have scoped access to all relevant in-space context, including content from the Coherence, Agreements, Members, and Treasury tabs, plus space metadata (purpose, tags, links).

I also added a requirement that for each signal, the AI can analyze the associated Matrix discussion (right panel conversation) and use it as evidence to derive new coherent signals.

Implemented in:

• docs/requirements/ai-left-panel-space-context-requirements.md
  • Section 7.4 Space Knowledge and Retrieval (FR-13A/FR-13B/FR-13C)
  • Acceptance criteria expanded (AC-4A/AC-4B)
  • Request context contract updated with knowledge scopes.