Current status
In development as a portable Universal I/O module.
Available now
The architecture, standalone mode, and safe boundaries are available for a focused discussion. No implemented runtime is claimed.
Limited
- is not “magic AI that decides everything” and does not replace product truth
- does not require AI, S.Y.S., or DAG
- is not only a Telegram bot, website backend, or Vercel integration
- does not become a DAG proxy
- does not confirm payments, issue licenses, or grant access by itself without a downstream module
Planned / in development
- Universal Intake Event
- Questionnaire Engine / Studio MVP
- Soul Profile Contract
- optional AI Consultant mode
- optional S.Y.S. Memory connector
- Channel Adapter SDK
- Module Connectors
- Setup Wizard
- packaged self-hosted delivery
Good fit if...
- You need a structured entry layer for requests, forms, or conversations.
- You want portable intake logic across channels.
- You are comfortable discussing a product still in development.
Not a fit if...
- You need a finished production intake platform today.
- You expect automatic payment, license, or access activation from the site.
In plain English
People arrive with different needs and explain them differently. A basic form only sends a message, while a basic bot replies in one chat. Intake helps identify the person and product, collect missing details, store the request, show status, and choose a safe next step — without unsafe promises or dependence on one external service.
What Intake does
- Receive a request, question, application, questionnaire, or conversation
- Identify the product and ask a follow-up question
- Store answers and status, then return a safe “request received” receipt
- Route the request to a human for manual review
- Connect an AI consultant only when configured
- Use S.Y.S. memory only when connected
- Create a safe DAG handoff for checkout or access
- Route work to ASA, AI-Mama, Iskra, or another module
- Keep baseline operation without AI, memory, or external connectors
Why it exists
- receive product applications and pre-consultation questionnaires
- avoid losing requests across channels
- give the user a clear next step
- separate intake, consultation, payment, access, memory, and execution
- use AI as a consultant rather than a source of truth
- keep an audit trail of what arrived, when, from whom, and what happened next
How it works
Channel → Intake → Decision → Response
- A channel receives input.
- Intake normalizes it into a Universal Intake Event.
- Intake validates the data and finds missing details.
- Rules choose the next step: a question, storage, manual review, or handoff.
- The user gets a safe response: received, more information needed, or sent for review.
Not tied to one website
BennuLabsSite is only one possible consumer of Intake. Telegram is only one channel, and Vercel is only one deployment option. Intake is being designed for websites, Telegram, APIs, embedded forms, admin UIs, CLIs, future messengers, voice interfaces, and other channels.
AI is optional
Standalone Intake receives input, validates data, stores state, returns safe responses, and routes requests without AI. When connected, AI remains a consultant; configuration, rules, memory, statuses, and audit events remain the sources of truth.
Operating modes
Standalone Intake
Baseline operation without required external services: applications, questionnaires, API intake, statuses, safe receipts, and manual review.
Intake + Soul
A configurable “soul” defines character, tone, allowed claims, boundaries, human escalation, and sources of truth. It is governed behavior, not random prompt text.
Intake + AI Consultant
An optional consultant asks follow-up questions, explains choices, helps select a path, and prepares summaries. It does not issue licenses, confirm payments, grant access, or replace product truth.
Intake + S.Y.S. Memory
Optional memory stores history, preferences, and follow-up context. If S.Y.S. is unavailable, Intake safely returns to standalone/degraded mode.
Intake + Bennu Organs
Intake is the ears, mouth, and small brain; S.Y.S. is memory; an AI model is the consultant; ASA is the hands; AI-Mama is the orchestrator; Iskra provides identity/persona; DAG provides payment, access, license, and event graph flows. Site and Telegram remain channels. Each module can work independently.
Questionnaire Studio
Questionnaire Studio is a planned visual questionnaire builder. Without hand-written JSON, clients will be able to start from a template, add text/email/textarea/select/checkbox/boolean fields, required settings, hints, and validation, preview and publish or unpublish, copy a hosted link, embed snippet, or API endpoint, view submission status, and export data. Questionnaires are planned for any website, Telegram flow, API, admin/manual intake, and future channels.
Example use cases
Product application
A structured submission and confirmation instead of a messy email.
Pre-consultation flow
Questions about goals, constraints, budget, urgency, privacy, and deployment preference.
AI consultant
Help choosing within configured rules and honest product boundaries.
Checkout or access handoff
A ready request can go to DAG without Intake itself confirming payment or granting access.
Memory through S.Y.S.
Previous context means each follow-up does not have to start from zero.
What Intake does not do
- is not “magic AI that decides everything” and does not replace product truth
- does not require AI, S.Y.S., or DAG
- is not only a Telegram bot, website backend, or Vercel integration
- does not become a DAG proxy
- does not confirm payments, issue licenses, or grant access by itself without a downstream module
Who it is for and why it matters
For products, services, and AI systems that need to collect requests cleanly across channels, explain the next step, keep an audit trail, retain control over AI, and deploy a portable module self-hosted or in client infrastructure.
Intake keeps new channels, memory, checkout, statuses, and AI from turning the inbound flow into a pile of temporary patches.
Product status and roadmap
Intake is being developed as a portable Universal I/O module.
- Universal Intake Event
- Questionnaire Engine / Studio MVP
- Soul Profile Contract
- optional AI Consultant mode
- optional S.Y.S. Memory connector
- Channel Adapter SDK
- Module Connectors
- Setup Wizard
- packaged self-hosted delivery
Proof & Evidence Status
Claim Snapshot: Verified (VERIFIED)
Product claim source snapshot in Intake repository reviewed. (Reviewed: 2026-09-28)
Runtime / Operational Proof: Not Yet Verified (NOT_YET_VERIFIED)
Architecture and design phase product; no implemented runtime is claimed
Explicit Operational Boundaries:- Planned flows are not an implemented runtime
- Legacy Telegram Lead Bot is reference only
- Model reasoning is not organizational truth
FAQ
Can Intake be used now?
Baseline Intake is being developed as a standalone module. Capabilities depend on mode, deployment, and connected components.
Is this just a request form?
No. A form is only one way to send data into the shared intake workflow.
Is this a Telegram bot?
No. Telegram can be one adapter, but Intake is not a Telegram-only product.
Does it need AI?
No. AI is an optional consultant.
Does it need S.Y.S.?
No. It is an optional memory layer; Intake works standalone without it.
Does it need DAG?
No. DAG is an optional connector for checkout, access, license, and event graph flows. Intake is not a DAG proxy.
Can it be embedded in another website?
Yes. Hosted forms, embedded widgets, and API endpoints are target roadmap scenarios.
Can it be self-hosted?
Yes. The target delivery is a portable, self-hosted/deployable module.
Need a proper entry layer for your product?
Intake builds the path from a first message to a structured request, safe receipt, manual review, memory, checkout handoff, or another module.
