snipara-business

snipara-business helps an LLM desktop client gather local or mounted Drive/SharePoint files, classify them by source authority, and prepare verified context before the LLM drafts a final deliverable.

What it is for

old offers, proposal archives, PowerPoints, and templates
current RFP folders and annexes
local or mounted Drive and SharePoint exports
technical diagrams, notes, and client-specific context

For GitHub repositories, use create-snipara --github instead.

Start with Context + Memory

New users can start directly with npx snipara-business init. If no Snipara auth is configured yet, it starts the same Context + Memory onboarding used by create-snipara, then prepares company and mission context from business files.

Core rule

Snipara prepares verified context. The LLM produces final documents.

Install

npx snipara-business --help

New account onboarding

Use this path when the workspace does not yet have reusable company context. The user can point their LLM to old offers, PowerPoints, templates, diagrams, and approved commercial documents. If the account is missing, the init command starts account/auth setup first.

npx snipara-business init

npx snipara-business bootstrap-company ~/Documents/Sales --write company-manifest.json

Old offers and decks are source material, not approved truth. The manifest flags stale pricing, private client references, unsupported claims, and binary sources that need extraction before promotion.

Authority policy

Rank	Source	Rule
1	Current RFP and annexes	Authoritative request. Never override it with templates.
2	Active client context	Current client truth: notes, constraints, diagrams, emails, decisions.
3	Current technical diagrams	Authoritative architecture evidence for feasibility, dependencies, risks, and solution design.
4	Business Response Playbook	Mandatory response rules and review policy.
5	Offer Templates	Reusable structure, not client-specific truth.
6	Business Library and Company Presentations	Approved positioning, methodology, examples, and language.
7	Reference Diagrams and past projects	Precedent only. Useful for patterns, never proof of the current scope.

Existing account workflow

Use this path when Business Context already exists and the user needs a verified pack for a live mission such as an RFP, proposal, audit, onboarding, or due diligence task.

npx snipara-business prepare-mission ~/Documents/ACME \

  --mission-name "ACME ERP Integration RFP" \

  --workflow rfp_response \

 --write acme-context-manifest.json

Command guide

init: prepare the local business scaffolding and wrap Context + Memory onboarding when needed
doctor: verify Hosted MCP access and optional runtime readiness
manifest: preview how a folder is classified
bootstrap-company: build reusable company context from historical material
prepare-mission: build a mission-specific manifest for a live task
prompt company / prompt mission: print prompt scaffolds for the LLM extraction step

What the manifest contains

Source inventory with local paths, hashes, timestamps, and supported parser formats.
Authority lanes for current request, client truth, diagrams, playbook, templates, library, and precedent.
Review flags for ambiguous files, old pricing, legal content, private references, and binary extraction.
Next actions for the LLM before drafting or uploading.

Review before apply

Keep --apply behind review. The manifest should be checked for stale pricing, private references, unsupported claims, binary extraction gaps, and misplaced authority lanes before promoting anything into verified context.

RLM Runtime

snipara-business can build manifests without RLM Runtime. Add RLM Runtime when the workflow needs sandboxed execution, transformation, duplicate detection, or proof traces.

npx snipara-business doctor --runtime-doctor