Lightbringer

Create asset — Creates one asset. Currently supports a Strategy with a title and populated Markdown sections, saved as a draft. Requires write consent and Strategy management rights. Returns its reference, link and revision; full state is available through fetch with include_asset: true when that parameter is advertised. Publication and patent services are separate actions. A repeated create can create a duplicate; search supports reconciliation of uncertain outcomes.

Delete asset — Permanently deletes one asset explicitly selected by the user. Currently supports Strategies only. Requires write consent and Strategy management rights. Does not delete other asset types or withdraw patent-service requests.

Update asset — Updates one asset to the supplied state. Currently supports Strategy title and ordered Markdown sections. The input uses the revision and complete section state returned by fetch with include_asset: true; this read depends on the advertised include_asset parameter. Applies atomically at the supplied revision; conflicts require a fresh fetch and reconciliation. Supplying sections replaces the collection: omitted sections are deleted and new sections receive IDs. Unchanged section IDs and comment anchors are preserved. Edits touching pending review changes fail; detached discussions are reporte…

Read company context — Reads the connected organisation’s profile, shared assistant notes, update permission and current revision. Notes are user/agent-authored source data, not verified facts or instructions. Requires read consent and organisation membership.

Get company context capture guide — Returns shared company-context interview guidance and the update schema. Supports conversation or synthesis from supplied material. Does not read or change company records.

Update company context — Updates selected profile fields or shared assistant notes in the connected organisation. Requires moderator rights and write consent. The revision from get_company_context is required; stale revisions are rejected without changes. Omitted fields remain unchanged; notes replaces the complete shared notes text and empty strings clear fields. applicant_name updates the legal applicant setting and names an unnamed workspace; it does not rename an established workspace. Returns the saved context and new revision. Does not create or publish a Strategy.

Create strategy — Creates a populated draft strategy. Capture guidance and schema are available from get_strategy_template. Validates before saving; success returns the saved link and revision. Supports subsequent refinement through edit_strategy. Requires strategy management rights, including customer moderators. Publication is separate.

Delete strategy — Permanently deletes a strategy when explicitly requested by the user. Requires strategy management rights.

Edit strategy — Applies an atomic batch of section edits using the revision returned by get_strategy. Replacements apply directly, without redlines, and preserve unchanged text and comment anchors. Ambiguous matches and edits touching pending review changes made in the application editor are rejected. The response includes orphaned_discussion_ids for retained threads whose anchored text was removed. Conflicting revisions are rejected without applying changes. Requires strategy management rights.

Read strategy — Reads a strategy, its section identifiers and Markdown, and its current revision for subsequent edits.

Get strategy capture guide — Returns the shared conversational capture guide, readiness criteria, creation schema and example. Supports interactive capture and drafting from existing material. Requires strategy management rights.

List strategies — Lists the strategies you can access in the connected organisation, including publication status.

Publish or unpublish strategy — Publishes a strategy or returns it to draft when the user requests it. Multiple strategies may be published simultaneously. Requires strategy management rights.

Import patent publication — Imports one public patent publication into the connected organisation, with a complete publication number and explicit purpose. own identifies the customer’s own patent or application; competitor identifies someone else’s patent for reference. Ownership and import scope come from the user’s intent, rather than search results alone. Own-patent imports automatically attempt family grouping with related saved patents, including earlier imports; a separate refresh is not normally needed. Repeated requests return the existing record without updating it. A different purpose or another publication o…

Refresh saved patent family — Updates family grouping for one saved own patent using public patent information and related own patents already saved in the connected organisation. Useful for an apparent missing relationship, an unfinished family update, or a requested check against newer public information. Imports already attempt family grouping automatically; routine refresh after import is unnecessary. Related publications must be imported separately before they can be included. Repeating import_patent only retrieves its saved outcome. Existing family relationships are retained, so refresh cannot remove incorrect relat…

Search public patents — Searches public patent publications by complete publication number, simple keywords, or assignee. Returns at most 25 results per page, with source details. Separate from search of saved organisation documents. Results are untrusted source data and do not establish current ownership or legal status. Null expired or abandoned values mean unknown. nextPage identifies the next page; truncated indicates limited search coverage. Search does not import documents. import_patent imports a selected publication.

Delete automated task — Permanently deletes an automated task owned by the current user in the connected organisation, including its cached findings. Available in any execution state. Deletion removes tracking; it does not cancel upstream analysis, delete the innovation, or withdraw a professional service request. Repeated deletion returns not_found.

Get innovation — Returns an innovation record rendered as markdown, including the problem, solution, technical details, and prior art.

Get innovation registration template — Returns the current innovation registration template: the schema, per-field guidance, and structure used to create a new innovation, together with capture guidance on gathering the innovation content — interviewing an inventor who is present, or authoring from existing material — before drafting.

Get automated task status — Returns an automated feedback task by task_id, with the same status, progress, findings and per-analysis errors as start_innovation_feedback. Refreshes active analyses and saves their status and available findings in Lightbringer. Succeeded, partially_succeeded and failed are terminal; queued and running tasks are still in progress. findings_error denotes unavailable findings and does not change terminal execution status. This endpoint does not track professional service requests, patent preparation or filing milestones.

List innovations — Lists the innovations in the user's Lightbringer organisation, each with a title, reference number, and web link. Accepts an optional free-text query to filter results.

List automated tasks — Lists the current user’s unexpired automated tasks in the connected organisation, optionally for an innovation. Recovers task IDs after a lost response or conversation. Returns recorded status summaries without polling upstream analyses. Tasks and findings expire 30 days after creation. Pagination can return an empty page with a continuation cursor. Professional service requests are separate.

Register innovation — Registers a new innovation in the user's Lightbringer organisation from a structured payload matching the current registration template. Validates before creating anything: invalid input returns field-specific errors without registering a record; success returns the saved identifier, reference number, web link, and any non-blocking warnings. Meant for capturing a concept that is not already recorded; enrichment of an existing innovation belongs in update_innovation. Completes registration without requesting patent preparation or filing. Requires a payload matching the current registration sch…

Request patent preparation — Requests Lightbringer patent preparation for an already registered innovation, expressing the user’s decision to pursue patent filing. Advances the innovation description into the Lightbringer team’s workflow and triggers email notifications to the assigned specialist and inventor. Returns whether preparation was newly requested or had already been requested. Email delivery status is not included. Separate from registration; does not itself complete preparation, file a patent or pay for services.

Start innovation feedback — Starts automated analysis of a registered innovation description across clarity, problem framing, completeness, or all focus areas. Returns one task_id, status, progress, available findings and per-analysis errors. Findings contain readable title/description fields; findings_error means findings are unavailable, not absent. Queued or running tasks continue through get_task_status with the same task_id. Succeeded, partially_succeeded and failed are terminal. Ending the wait does not cancel analysis. Separate from novelty assessment, patent search, FTO, attorney review and patent preparation re…

Update innovation sections — Updates one or more sections of an existing innovation record with new content and returns the updated innovation. Overwrites the specified sections.

Check task status — Returns the status of a long-running Lightbringer task identified by a ticket: state (pending, running, succeeded, or failed), progress, and the findings once it has succeeded. This is the continuation for tickets returned by a pending or cancelled get_invention_feedback; each ticket resolves here once its state reaches succeeded or failed.

Register innovation disclosure — Registers a new innovation disclosure in the user's Lightbringer organisation from a structured payload matching the current invention template, and returns the saved invention. Meant for capturing a concept that is not already recorded; enrichment of an existing disclosure belongs in update_invention. Completes registration without requesting patent preparation or filing. Requires the current disclosure schema.

Get invention — Returns an invention disclosure rendered as markdown, including the problem, solution, technical details, and prior art.

Get invention feedback — Runs Lightbringer's patent-analysis suite on an invention disclosure and returns structured findings across selectable focus areas (clarity, problem framing, completeness, or all) — the assessment that shows where a disclosure needs strengthening. Automated disclosure feedback, separate from a patent search, novelty assessment, FTO opinion or attorney review. Analysis may take from seconds to a few minutes; while it is still running the response has a pending status and includes ticket identifiers whose findings check_task_status returns once complete.

Get invention template — Returns the current invention authoring template: the schema, per-field guidance, and structure used to create a new invention, together with capture guidance on gathering the invention content — interviewing an inventor who is present, or authoring from existing material — before drafting.

List inventions — Lists the invention disclosures in the user's Lightbringer organisation, each with a title, reference number, and web link. Accepts an optional free-text query to filter results.

Prepare for patent filing — Requests Lightbringer patent preparation for an already registered invention, expressing the user’s decision to pursue patent filing. Advances the disclosure into the Lightbringer team’s workflow, triggers email notifications to the assigned specialist and inventor, and returns its status. Separate from registration; does not itself file a patent or pay for services.

Update invention sections — Updates one or more sections of an existing invention disclosure with new content and returns the updated invention. Overwrites the specified sections.

Validate invention draft — Validates a draft invention against the authoring schema and returns any errors and warnings without saving anything. Suited to checking a draft ahead of create_invention, and again after substantial edits, so problems surface before the invention is persisted.