{
  "schemaVersion": "1.1.0",
  "language": "en",
  "revision": "b3ac61685aa3582f589ca5bef8a3ddb2f0897bf58ce9e91c0aabddfdc3d67587",
  "updatedAt": "2026-11-20T15:57:48.841Z",
  "publisher": "LIVE4K / BizWants",
  "interpretation": {
    "scope": "English editorial profiles of LIVE4K and BizWants projects and services. Only current translations of published source profiles are included.",
    "capabilityStatus": {
      "documented": "Described in reviewed source material; not an independent operational test.",
      "owner-described": "Described by the owner or adapted from the public business profile; the confirmed scope may be narrower.",
      "proposed": "A possible use case or connection; not an established delivered feature."
    },
    "benefits": "Benefits and use cases are expected outcomes and evaluation ideas, not customer references, measured results or guarantees.",
    "availability": "A public description of an internal project does not grant application access. Features, integrations, capacity, schedules and support require a specific agreement.",
    "evidence": "Evidence IDs are local to each project. A review date refers to source review rather than live service status.",
    "missingInformation": "An empty list means information is not documented in this edition. Do not invent prices, guarantees or certifications.",
    "relationships": "Related projects are editorial context. Synergy scoring and business actions belong to the consuming system.",
    "domains": {
      "digital-content": "Digital content",
      "event-production": "Event production",
      "lighting": "Lighting",
      "live-video": "Live video",
      "language-access": "Language access",
      "customer-relationships": "CRM and relationships",
      "ai-workforce": "AI workflows",
      "remarketing": "Equipment resale",
      "custom-software": "Custom software",
      "infrastructure": "Infrastructure",
      "hardware": "Hardware",
      "digital-fabrication": "Digital fabrication",
      "water-monitoring": "Water monitoring",
      "simulation-training": "Simulation training"
    }
  },
  "audience": "public",
  "projects": [
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "agents",
        "name": "Digital employees",
        "brand": "LIVE4K",
        "kind": "internal-project",
        "availability": "internal-only",
        "website": "https://agents.live4k.media/",
        "summary": "LIVE4K’s internal platform for agent teams, tasks, preparation and approvals. We use the experience to design controlled business processes and limited IT tools.",
        "what": "We explore how teams of AI agents can receive tasks, prepare materials and use clearly bounded tools. The platform is an internal LIVE4K project and a source of implementation experience.",
        "why": "Useful automation needs more than a model response. It needs a clear task, access limits, review points and a way to distinguish a proposal from an action that changes another system.",
        "who": [
          "Businesses exploring controlled AI automation",
          "Teams with repetitive research or preparation work",
          "IT owners defining tool access and approval responsibilities"
        ],
        "where": "Our internal environment. Any customer-facing implementation, access or deployment is a separately agreed project.",
        "when": "When you want to assess a bounded workflow for AI assistance and can define inputs, responsibilities and acceptance criteria.",
        "how": [
          "Identify one task, its inputs and its limits.",
          "Agree tools, permissions, outputs and human review.",
          "Test the proposed flow on an appropriate limited scope.",
          "Review quality, failure cases and the conditions for any next step."
        ],
        "differentiators": [
          "Internal use informs the design of real workflows.",
          "Agent work connects to our software, integrations and infrastructure experience."
        ],
        "benefits": [
          "Practical experience for designing an AI pilot",
          "Clearer separation of preparation, review and action",
          "A basis for defining tool permissions and operating responsibilities"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Agent teams and tasks",
            "description": "Organise work around defined tasks and cooperating agent roles.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Preparation of materials",
            "description": "Use agents to prepare information and proposals for further review.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Approvals",
            "description": "Place human approval at the steps that require it.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Bounded tools",
            "description": "Design narrowly scoped IT tools rather than unrestricted access to business systems.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Operations teams",
            "need": "Reduce repetitive preparation",
            "solution": "Assess a limited agent-assisted workflow with review before consequential steps.",
            "expectedBenefit": "A practical basis for deciding what to automate."
          },
          {
            "audience": "IT teams",
            "need": "Define safe tool access",
            "solution": "Design narrow interfaces and explicit approval boundaries.",
            "expectedBenefit": "A clearer operating model for a pilot."
          }
        ],
        "limitations": [
          "The described platform is internal; the public profile does not provide access or imply a ready-made subscription.",
          "New tools, customer deployments and integrations require separate design and validation.",
          "Outputs and external actions need the review and responsibility agreed for the use case."
        ],
        "tags": [
          "Digital employees",
          "ai-workforce",
          "customer-relationships",
          "infrastructure"
        ],
        "relatedProjectIds": [
          "software",
          "infrastructure",
          "remarketagent",
          "forge"
        ],
        "details": {
          "aliases": [
            "Digital employees",
            "AI agents for controlled business workflows"
          ],
          "domainIds": [
            "ai-workforce",
            "customer-relationships",
            "infrastructure"
          ],
          "positioning": {
            "category": "AI agents for controlled business workflows",
            "elevatorPitch": "LIVE4K’s internal platform for agent teams, tasks, preparation and approvals. We use the experience to design controlled business processes and limited IT tools.",
            "marketRole": "We explore how teams of AI agents can receive tasks, prepare materials and use clearly bounded tools. The platform is an internal LIVE4K project and a source of implementation experience.",
            "offeringBoundaries": [
              "The described platform is internal; the public profile does not provide access or imply a ready-made subscription.",
              "New tools, customer deployments and integrations require separate design and validation.",
              "Outputs and external actions need the review and responsibility agreed for the use case."
            ]
          },
          "readiness": {
            "commercialStatus": "internal-only",
            "documentedState": "We explore how teams of AI agents can receive tasks, prepare materials and use clearly bounded tools. The platform is an internal LIVE4K project and a source of implementation experience.",
            "notEstablished": [
              "The described platform is internal; the public profile does not provide access or imply a ready-made subscription.",
              "New tools, customer deployments and integrations require separate design and validation.",
              "Outputs and external actions need the review and responsibility agreed for the use case."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "We explore how teams of AI agents can receive tasks, prepare materials and use clearly bounded tools. The platform is an internal LIVE4K project and a source of implementation experience."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Businesses exploring controlled AI automation",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Businesses exploring controlled AI automation"
              ],
              "pains": [
                "Useful automation needs more than a model response. It needs a clear task, access limits, review points and a way to distinguish a proposal from an action that changes another system."
              ],
              "triggers": [
                "When you want to assess a bounded workflow for AI assistance and can define inputs, responsibilities and acceptance criteria."
              ],
              "fitConditions": [
                "A clearly bounded process and authorised owner",
                "Appropriate sample inputs, review criteria and access restrictions"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Teams with repetitive research or preparation work",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Teams with repetitive research or preparation work"
              ],
              "pains": [
                "Useful automation needs more than a model response. It needs a clear task, access limits, review points and a way to distinguish a proposal from an action that changes another system."
              ],
              "triggers": [
                "When you want to assess a bounded workflow for AI assistance and can define inputs, responsibilities and acceptance criteria."
              ],
              "fitConditions": [
                "A clearly bounded process and authorised owner",
                "Appropriate sample inputs, review criteria and access restrictions"
              ]
            },
            {
              "id": "audience-3",
              "segment": "IT owners defining tool access and approval responsibilities",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "IT owners defining tool access and approval responsibilities"
              ],
              "pains": [
                "Useful automation needs more than a model response. It needs a clear task, access limits, review points and a way to distinguish a proposal from an action that changes another system."
              ],
              "triggers": [
                "When you want to assess a bounded workflow for AI assistance and can define inputs, responsibilities and acceptance criteria."
              ],
              "fitConditions": [
                "A clearly bounded process and authorised owner",
                "Appropriate sample inputs, review criteria and access restrictions"
              ]
            }
          ],
          "systemModel": {
            "principle": "We explore how teams of AI agents can receive tasks, prepare materials and use clearly bounded tools. The platform is an internal LIVE4K project and a source of implementation experience.",
            "components": [
              {
                "id": "component-1",
                "name": "Agent teams and tasks",
                "purpose": "Organise work around defined tasks and cooperating agent roles.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Preparation of materials",
                "purpose": "Use agents to prepare information and proposals for further review.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Approvals",
                "purpose": "Place human approval at the steps that require it.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Bounded tools",
                "purpose": "Design narrowly scoped IT tools rather than unrestricted access to business systems.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "A clearly bounded process and authorised owner",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Appropriate sample inputs, review criteria and access restrictions",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "A workflow proposal or separately agreed pilot",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Defined controls and evaluation criteria",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Choose a bounded use case",
                "description": "Identify one task, its inputs and its limits.",
                "customerContribution": [],
                "providerContribution": [
                  "Identify one task, its inputs and its limits."
                ],
                "outputNames": [
                  "Choose a bounded use case"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Define control points",
                "description": "Agree tools, permissions, outputs and human review.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree tools, permissions, outputs and human review."
                ],
                "outputNames": [
                  "Define control points"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Prepare a pilot",
                "description": "Test the proposed flow on an appropriate limited scope.",
                "customerContribution": [],
                "providerContribution": [
                  "Test the proposed flow on an appropriate limited scope."
                ],
                "outputNames": [
                  "Prepare a pilot"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Evaluate the result",
                "description": "Review quality, failure cases and the conditions for any next step.",
                "customerContribution": [],
                "providerContribution": [
                  "Review quality, failure cases and the conditions for any next step."
                ],
                "outputNames": [
                  "Evaluate the result"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "A separately scoped discussion or evaluation; access is not implied."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "A clearly bounded process and authorised owner",
              "Appropriate sample inputs, review criteria and access restrictions"
            ],
            "customerResponsibilities": [
              "A clearly bounded process and authorised owner",
              "Appropriate sample inputs, review criteria and access restrictions"
            ],
            "providerResponsibilities": [
              "A workflow proposal or separately agreed pilot",
              "Defined controls and evaluation criteria"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "The described platform is internal; the public profile does not provide access or imply a ready-made subscription.",
              "New tools, customer deployments and integrations require separate design and validation.",
              "Outputs and external actions need the review and responsibility agreed for the use case."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Business and IT tools",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Any new connector needs an explicit permission model and implementation scope.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "Practical experience for designing an AI pilot",
              "mechanism": "Useful automation needs more than a model response. It needs a clear task, access limits, review points and a way to distinguish a proposal from an action that changes another system.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Clearer separation of preparation, review and action",
              "mechanism": "Useful automation needs more than a model response. It needs a clear task, access limits, review points and a way to distinguish a proposal from an action that changes another system.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "A basis for defining tool permissions and operating responsibilities",
              "mechanism": "Useful automation needs more than a model response. It needs a clear task, access limits, review points and a way to distinguish a proposal from an action that changes another system.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When you want to assess a bounded workflow for AI assistance and can define inputs, responsibilities and acceptance criteria."
            ],
            "poorFitSignals": [
              "The described platform is internal; the public profile does not provide access or imply a ready-made subscription.",
              "New tools, customer deployments and integrations require separate design and validation.",
              "Outputs and external actions need the review and responsibility agreed for the use case."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "The described platform is internal; the public profile does not provide access or imply a ready-made subscription.",
              "New tools, customer deployments and integrations require separate design and validation.",
              "Outputs and external actions need the review and responsibility agreed for the use case."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Can we log in to the platform?",
              "answer": "The public profile describes an internal LIVE4K project. Customer access or a separate implementation must be discussed independently.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Can an agent act without approval?",
              "answer": "The appropriate approval rules depend on the task. We define those rules and tool permissions explicitly when designing a workflow.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/ai-agents-business-workflows/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "digi-production",
        "name": "LIVE4K digital production",
        "brand": "LIVE4K",
        "kind": "service",
        "availability": "by-arrangement",
        "website": "https://live4k.media/",
        "summary": "Creative content for businesses: video, photography, graphics, VR180/360 and live streaming, from the first idea to the finished deliverable.",
        "what": "We plan and produce digital content around a communication goal. A project can combine filming, still photography, graphic design and immersive formats, with the technical setup chosen for the intended audience and channels.",
        "why": "Separate suppliers and disconnected outputs make it harder to maintain a consistent story. Bringing creative preparation and technical production together helps your team turn one brief into materials it can actually use.",
        "who": [
          "Business marketing and communications teams",
          "Agencies and production partners",
          "Organisations explaining complex products or services"
        ],
        "where": "At your premises, on location and in suitable production environments in Czechia or abroad. Post-production can be coordinated remotely.",
        "when": "When you are launching a product, explaining expertise, documenting an event or refreshing your company communication.",
        "how": [
          "Agree the audience, message, channels and deliverables.",
          "Plan locations, contributors, access and the filming schedule.",
          "Capture the agreed video, photography or immersive scenes.",
          "Review the work and deliver the agreed formats and versions."
        ],
        "differentiators": [
          "Creative work connects directly to our AV and software capabilities.",
          "We can plan on-site production and subsequent technical distribution together."
        ],
        "benefits": [
          "A consistent story across agreed formats",
          "One coordinated production brief and handover",
          "Materials prepared for their intended channels"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Video production",
            "description": "Preparation, filming and post-production for business communication.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Photography and graphics",
            "description": "Still images and graphic materials aligned with the purpose of the project.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Immersive formats",
            "description": "VR180 and 360-degree content where the viewing environment and subject make these formats useful.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Connected event content",
            "description": "Combine filming with event production and live streaming when the assignment calls for it.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Marketing teams",
            "need": "Explain a technical offering clearly",
            "solution": "Combine an interview, product footage and graphics into an agreed content package.",
            "expectedBenefit": "More useful material for consistent communication."
          },
          {
            "audience": "Event organisers",
            "need": "Keep using content after the event",
            "solution": "Plan interviews and recording alongside technical event production.",
            "expectedBenefit": "A coherent collection of reusable outputs."
          }
        ],
        "limitations": [
          "Rights, contributor permissions and publication responsibilities must be agreed.",
          "VR hardware, media placement and ongoing campaign management are separate scope decisions.",
          "Formats, languages, revisions and delivery dates are agreed for each project."
        ],
        "tags": [
          "LIVE4K digital production",
          "digital-content",
          "live-video"
        ],
        "relatedProjectIds": [
          "podcasts",
          "events",
          "stream"
        ],
        "details": {
          "aliases": [
            "LIVE4K digital production",
            "Video, photography and digital production"
          ],
          "domainIds": [
            "digital-content",
            "live-video"
          ],
          "positioning": {
            "category": "Video, photography and digital production",
            "elevatorPitch": "Creative content for businesses: video, photography, graphics, VR180/360 and live streaming, from the first idea to the finished deliverable.",
            "marketRole": "We plan and produce digital content around a communication goal. A project can combine filming, still photography, graphic design and immersive formats, with the technical setup chosen for the intended audience and channels.",
            "offeringBoundaries": [
              "Rights, contributor permissions and publication responsibilities must be agreed.",
              "VR hardware, media placement and ongoing campaign management are separate scope decisions.",
              "Formats, languages, revisions and delivery dates are agreed for each project."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "We plan and produce digital content around a communication goal. A project can combine filming, still photography, graphic design and immersive formats, with the technical setup chosen for the intended audience and channels.",
            "notEstablished": [
              "Rights, contributor permissions and publication responsibilities must be agreed.",
              "VR hardware, media placement and ongoing campaign management are separate scope decisions.",
              "Formats, languages, revisions and delivery dates are agreed for each project."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "We plan and produce digital content around a communication goal. A project can combine filming, still photography, graphic design and immersive formats, with the technical setup chosen for the intended audience and channels."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Business marketing and communications teams",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Business marketing and communications teams"
              ],
              "pains": [
                "Separate suppliers and disconnected outputs make it harder to maintain a consistent story. Bringing creative preparation and technical production together helps your team turn one brief into materials it can actually use."
              ],
              "triggers": [
                "When you are launching a product, explaining expertise, documenting an event or refreshing your company communication."
              ],
              "fitConditions": [
                "Communication goal, audience and intended channels",
                "Access to locations, contributors and an authorised reviewer"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Agencies and production partners",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Agencies and production partners"
              ],
              "pains": [
                "Separate suppliers and disconnected outputs make it harder to maintain a consistent story. Bringing creative preparation and technical production together helps your team turn one brief into materials it can actually use."
              ],
              "triggers": [
                "When you are launching a product, explaining expertise, documenting an event or refreshing your company communication."
              ],
              "fitConditions": [
                "Communication goal, audience and intended channels",
                "Access to locations, contributors and an authorised reviewer"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Organisations explaining complex products or services",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Organisations explaining complex products or services"
              ],
              "pains": [
                "Separate suppliers and disconnected outputs make it harder to maintain a consistent story. Bringing creative preparation and technical production together helps your team turn one brief into materials it can actually use."
              ],
              "triggers": [
                "When you are launching a product, explaining expertise, documenting an event or refreshing your company communication."
              ],
              "fitConditions": [
                "Communication goal, audience and intended channels",
                "Access to locations, contributors and an authorised reviewer"
              ]
            }
          ],
          "systemModel": {
            "principle": "We plan and produce digital content around a communication goal. A project can combine filming, still photography, graphic design and immersive formats, with the technical setup chosen for the intended audience and channels.",
            "components": [
              {
                "id": "component-1",
                "name": "Video production",
                "purpose": "Preparation, filming and post-production for business communication.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Photography and graphics",
                "purpose": "Still images and graphic materials aligned with the purpose of the project.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Immersive formats",
                "purpose": "VR180 and 360-degree content where the viewing environment and subject make these formats useful.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Connected event content",
                "purpose": "Combine filming with event production and live streaming when the assignment calls for it.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "Communication goal, audience and intended channels",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Access to locations, contributors and an authorised reviewer",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "Agreed edited video, photographs or graphic materials",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Output versions and files specified in the brief",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Define the brief",
                "description": "Agree the audience, message, channels and deliverables.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree the audience, message, channels and deliverables."
                ],
                "outputNames": [
                  "Define the brief"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Prepare production",
                "description": "Plan locations, contributors, access and the filming schedule.",
                "customerContribution": [],
                "providerContribution": [
                  "Plan locations, contributors, access and the filming schedule."
                ],
                "outputNames": [
                  "Prepare production"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Create the material",
                "description": "Capture the agreed video, photography or immersive scenes.",
                "customerContribution": [],
                "providerContribution": [
                  "Capture the agreed video, photography or immersive scenes."
                ],
                "outputNames": [
                  "Create the material"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Edit and hand over",
                "description": "Review the work and deliver the agreed formats and versions.",
                "customerContribution": [],
                "providerContribution": [
                  "Review the work and deliver the agreed formats and versions."
                ],
                "outputNames": [
                  "Edit and hand over"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "Communication goal, audience and intended channels",
              "Access to locations, contributors and an authorised reviewer"
            ],
            "customerResponsibilities": [
              "Communication goal, audience and intended channels",
              "Access to locations, contributors and an authorised reviewer"
            ],
            "providerResponsibilities": [
              "Agreed edited video, photographs or graphic materials",
              "Output versions and files specified in the brief"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Rights, contributor permissions and publication responsibilities must be agreed.",
              "VR hardware, media placement and ongoing campaign management are separate scope decisions.",
              "Formats, languages, revisions and delivery dates are agreed for each project."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Publishing workflow",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Deliver content for your website, presentation or communication channels in agreed formats.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "A consistent story across agreed formats",
              "mechanism": "Separate suppliers and disconnected outputs make it harder to maintain a consistent story. Bringing creative preparation and technical production together helps your team turn one brief into materials it can actually use.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "One coordinated production brief and handover",
              "mechanism": "Separate suppliers and disconnected outputs make it harder to maintain a consistent story. Bringing creative preparation and technical production together helps your team turn one brief into materials it can actually use.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Materials prepared for their intended channels",
              "mechanism": "Separate suppliers and disconnected outputs make it harder to maintain a consistent story. Bringing creative preparation and technical production together helps your team turn one brief into materials it can actually use.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When you are launching a product, explaining expertise, documenting an event or refreshing your company communication."
            ],
            "poorFitSignals": [
              "Rights, contributor permissions and publication responsibilities must be agreed.",
              "VR hardware, media placement and ongoing campaign management are separate scope decisions.",
              "Formats, languages, revisions and delivery dates are agreed for each project."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Rights, contributor permissions and publication responsibilities must be agreed.",
              "VR hardware, media placement and ongoing campaign management are separate scope decisions.",
              "Formats, languages, revisions and delivery dates are agreed for each project."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Can you work at our location?",
              "answer": "Yes, the production plan can be built around your premises or another suitable location. Access, sound, light and timing need to be checked.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Can one project include several formats?",
              "answer": "Yes. We agree the required video, photo, graphic or immersive outputs during preparation so the production supports them.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/video-photography-digital-production/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "events",
        "name": "Technical event production",
        "brand": "LIVE4K",
        "kind": "service",
        "availability": "by-arrangement",
        "website": "https://live4k.media/",
        "summary": "Stage, projection, sound, lighting, recording, photography, live streaming and technical support for interpretation, coordinated as one solution.",
        "what": "We prepare the technical production of conferences, company events and hybrid gatherings. The plan connects the venue, programme, speakers, on-site audience and online viewers.",
        "why": "An event depends on many systems working together at the right moment. Coordinating AV, signal paths and programme requirements helps the organiser manage the whole experience rather than a collection of disconnected suppliers.",
        "who": [
          "Conference and business event organisers",
          "Corporate communications teams",
          "Agencies needing a technical production partner"
        ],
        "where": "Event venues and temporary installations in Czechia and abroad, with remote participation where required.",
        "when": "When an event needs coordinated sound, picture, lighting, a live feed or several audience formats.",
        "how": [
          "Agree the audience, venue, timetable and required outputs.",
          "Define equipment, connections, responsibilities and setup time.",
          "Check signal paths and programme transitions in the actual venue.",
          "Operate the agreed production and deliver commissioned recordings or other outputs."
        ],
        "differentiators": [
          "AV production connects to our streaming, software and hardware capabilities.",
          "Language access can be planned with STAGE from BizWants where appropriate."
        ],
        "benefits": [
          "A coordinated technical plan for the event",
          "Fewer disconnected handovers between disciplines",
          "An opportunity to capture useful content alongside the live programme"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Technical planning",
            "description": "Translate the programme and venue conditions into an AV production plan.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "On-site AV",
            "description": "Coordinate sound, projection, lighting and camera production within the agreed setup.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Streaming and recording",
            "description": "Connect the event to online audiences and preserve agreed content for later use.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Interpretation support",
            "description": "Prepare the audio and technical connections required for the chosen interpretation or language-access solution.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Conference organisers",
            "need": "Serve both the room and online viewers",
            "solution": "Coordinate AV, camera direction and streaming in one technical plan.",
            "expectedBenefit": "A more coherent hybrid event."
          },
          {
            "audience": "Corporate teams",
            "need": "Retain the value of an internal event",
            "solution": "Plan recording, interviews and post-event material with the live production.",
            "expectedBenefit": "Useful content beyond the event day."
          }
        ],
        "limitations": [
          "Equipment, crew size, travel and operating hours are project-specific.",
          "Venue connectivity, power, access and safety responsibilities must be confirmed.",
          "Interpretation services and language availability depend on the chosen solution and agreement."
        ],
        "tags": [
          "Technical event production",
          "event-production",
          "live-video",
          "language-access"
        ],
        "relatedProjectIds": [
          "lighting",
          "stream",
          "stage",
          "digi-production",
          "podcasts"
        ],
        "details": {
          "aliases": [
            "Technical event production",
            "Technical production for events and conferences"
          ],
          "domainIds": [
            "event-production",
            "live-video",
            "language-access"
          ],
          "positioning": {
            "category": "Technical production for events and conferences",
            "elevatorPitch": "Stage, projection, sound, lighting, recording, photography, live streaming and technical support for interpretation, coordinated as one solution.",
            "marketRole": "We prepare the technical production of conferences, company events and hybrid gatherings. The plan connects the venue, programme, speakers, on-site audience and online viewers.",
            "offeringBoundaries": [
              "Equipment, crew size, travel and operating hours are project-specific.",
              "Venue connectivity, power, access and safety responsibilities must be confirmed.",
              "Interpretation services and language availability depend on the chosen solution and agreement."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "We prepare the technical production of conferences, company events and hybrid gatherings. The plan connects the venue, programme, speakers, on-site audience and online viewers.",
            "notEstablished": [
              "Equipment, crew size, travel and operating hours are project-specific.",
              "Venue connectivity, power, access and safety responsibilities must be confirmed.",
              "Interpretation services and language availability depend on the chosen solution and agreement."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "We prepare the technical production of conferences, company events and hybrid gatherings. The plan connects the venue, programme, speakers, on-site audience and online viewers."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Conference and business event organisers",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Conference and business event organisers"
              ],
              "pains": [
                "An event depends on many systems working together at the right moment. Coordinating AV, signal paths and programme requirements helps the organiser manage the whole experience rather than a collection of disconnected suppliers."
              ],
              "triggers": [
                "When an event needs coordinated sound, picture, lighting, a live feed or several audience formats."
              ],
              "fitConditions": [
                "Programme, venue details, audience format and schedule",
                "Access for preparation, agreed power and connectivity, and speaker materials"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Corporate communications teams",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Corporate communications teams"
              ],
              "pains": [
                "An event depends on many systems working together at the right moment. Coordinating AV, signal paths and programme requirements helps the organiser manage the whole experience rather than a collection of disconnected suppliers."
              ],
              "triggers": [
                "When an event needs coordinated sound, picture, lighting, a live feed or several audience formats."
              ],
              "fitConditions": [
                "Programme, venue details, audience format and schedule",
                "Access for preparation, agreed power and connectivity, and speaker materials"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Agencies needing a technical production partner",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Agencies needing a technical production partner"
              ],
              "pains": [
                "An event depends on many systems working together at the right moment. Coordinating AV, signal paths and programme requirements helps the organiser manage the whole experience rather than a collection of disconnected suppliers."
              ],
              "triggers": [
                "When an event needs coordinated sound, picture, lighting, a live feed or several audience formats."
              ],
              "fitConditions": [
                "Programme, venue details, audience format and schedule",
                "Access for preparation, agreed power and connectivity, and speaker materials"
              ]
            }
          ],
          "systemModel": {
            "principle": "We prepare the technical production of conferences, company events and hybrid gatherings. The plan connects the venue, programme, speakers, on-site audience and online viewers.",
            "components": [
              {
                "id": "component-1",
                "name": "Technical planning",
                "purpose": "Translate the programme and venue conditions into an AV production plan.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "On-site AV",
                "purpose": "Coordinate sound, projection, lighting and camera production within the agreed setup.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Streaming and recording",
                "purpose": "Connect the event to online audiences and preserve agreed content for later use.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Interpretation support",
                "purpose": "Prepare the audio and technical connections required for the chosen interpretation or language-access solution.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "Programme, venue details, audience format and schedule",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Access for preparation, agreed power and connectivity, and speaker materials",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "An operated technical setup for the agreed event",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Commissioned recordings, photographs or other agreed materials",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Understand the programme",
                "description": "Agree the audience, venue, timetable and required outputs.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree the audience, venue, timetable and required outputs."
                ],
                "outputNames": [
                  "Understand the programme"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Prepare the technical plan",
                "description": "Define equipment, connections, responsibilities and setup time.",
                "customerContribution": [],
                "providerContribution": [
                  "Define equipment, connections, responsibilities and setup time."
                ],
                "outputNames": [
                  "Prepare the technical plan"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Install and rehearse",
                "description": "Check signal paths and programme transitions in the actual venue.",
                "customerContribution": [],
                "providerContribution": [
                  "Check signal paths and programme transitions in the actual venue."
                ],
                "outputNames": [
                  "Install and rehearse"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Run and hand over",
                "description": "Operate the agreed production and deliver commissioned recordings or other outputs.",
                "customerContribution": [],
                "providerContribution": [
                  "Operate the agreed production and deliver commissioned recordings or other outputs."
                ],
                "outputNames": [
                  "Run and hand over"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "Programme, venue details, audience format and schedule",
              "Access for preparation, agreed power and connectivity, and speaker materials"
            ],
            "customerResponsibilities": [
              "Programme, venue details, audience format and schedule",
              "Access for preparation, agreed power and connectivity, and speaker materials"
            ],
            "providerResponsibilities": [
              "An operated technical setup for the agreed event",
              "Commissioned recordings, photographs or other agreed materials"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Equipment, crew size, travel and operating hours are project-specific.",
              "Venue connectivity, power, access and safety responsibilities must be confirmed.",
              "Interpretation services and language availability depend on the chosen solution and agreement."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "LIVE4K STREAM",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Connect live camera and audio sources to agreed streaming outputs.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "id": "integration-2",
              "name": "STAGE by BizWants",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Plan event audio and audience access for transcription, translation or interpretation.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "A coordinated technical plan for the event",
              "mechanism": "An event depends on many systems working together at the right moment. Coordinating AV, signal paths and programme requirements helps the organiser manage the whole experience rather than a collection of disconnected suppliers.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Fewer disconnected handovers between disciplines",
              "mechanism": "An event depends on many systems working together at the right moment. Coordinating AV, signal paths and programme requirements helps the organiser manage the whole experience rather than a collection of disconnected suppliers.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "An opportunity to capture useful content alongside the live programme",
              "mechanism": "An event depends on many systems working together at the right moment. Coordinating AV, signal paths and programme requirements helps the organiser manage the whole experience rather than a collection of disconnected suppliers.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When an event needs coordinated sound, picture, lighting, a live feed or several audience formats."
            ],
            "poorFitSignals": [
              "Equipment, crew size, travel and operating hours are project-specific.",
              "Venue connectivity, power, access and safety responsibilities must be confirmed.",
              "Interpretation services and language availability depend on the chosen solution and agreement."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Equipment, crew size, travel and operating hours are project-specific.",
              "Venue connectivity, power, access and safety responsibilities must be confirmed.",
              "Interpretation services and language availability depend on the chosen solution and agreement."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Can you cover a hybrid event?",
              "answer": "Yes. We plan the relationship between the venue production and the online audience, including connectivity and output requirements.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Can we receive a recording?",
              "answer": "Yes, recording and its final format should be included in the brief. Editing and additional versions are separate scope decisions.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/event-conference-technical-production/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "forge",
        "name": "Forge",
        "brand": "LIVE4K",
        "kind": "internal-project",
        "availability": "internal-only",
        "website": "https://forge.live4k.media/",
        "summary": "LIVE4K’s internal AI environment for parametric 3D design, visualisation, version history and STEP, STL and 3MF exports for subsequent engineering and print preparation.",
        "what": "Forge explores an AI-assisted route to parametric CAD models. It brings model preparation, visualisation, variant history and engineering exports into one internal design environment.",
        "why": "Moving between a design idea, its geometry and the next revision can create repeated manual work. A shared history and export workflow help make design iteration more organised.",
        "who": [
          "Teams exploring AI-assisted engineering workflows",
          "Designers assessing parametric modelling and variants",
          "Businesses connecting software with prototyping"
        ],
        "where": "An internal LIVE4K environment. Any external access or customer deployment needs a separate agreement.",
        "when": "When you want to assess AI assistance for a bounded modelling task or the handover from design to manufacturing preparation.",
        "how": [
          "Agree the geometry, parameters and intended use.",
          "Review the generated or edited design rather than assuming it is correct.",
          "Adjust parameters and compare the resulting versions.",
          "Check the required file format and downstream engineering work."
        ],
        "differentiators": [
          "Connects AI, parametric modelling and versioned design work.",
          "Sits alongside our hardware development and prototyping experience."
        ],
        "benefits": [
          "A more organised design iteration workflow",
          "Visible variants and a clearer handover to downstream tools",
          "Practical experience for assessing AI-assisted CAD"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Parametric modelling",
            "description": "Work with model parameters and editable design variations.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Visualisation",
            "description": "Review the proposed geometry in the design environment.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Version history",
            "description": "Keep track of variants and changes during iteration.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Engineering exports",
            "description": "Prepare STEP, STL and 3MF files for the next engineering or print-preparation step.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Prototyping teams",
            "need": "Explore several geometric variants",
            "solution": "Use parameters and version history to compare a bounded design.",
            "expectedBenefit": "A clearer design review process."
          },
          {
            "audience": "Engineering teams",
            "need": "Prepare a model for another tool",
            "solution": "Export and validate the agreed file format before further work.",
            "expectedBenefit": "A more explicit handover between design stages."
          }
        ],
        "limitations": [
          "Forge is an internal project, not a publicly available design subscription.",
          "Documentation supports CAD, versions and exports; it does not establish a live connection to a physical printer.",
          "Exported geometry needs qualified engineering and manufacturing checks."
        ],
        "tags": [
          "Forge",
          "digital-fabrication",
          "hardware",
          "ai-workforce"
        ],
        "relatedProjectIds": [
          "hardware",
          "agents",
          "simroom"
        ],
        "details": {
          "aliases": [
            "Forge",
            "Forge: AI-assisted parametric 3D design"
          ],
          "domainIds": [
            "digital-fabrication",
            "hardware",
            "ai-workforce"
          ],
          "positioning": {
            "category": "Forge: AI-assisted parametric 3D design",
            "elevatorPitch": "LIVE4K’s internal AI environment for parametric 3D design, visualisation, version history and STEP, STL and 3MF exports for subsequent engineering and print preparation.",
            "marketRole": "Forge explores an AI-assisted route to parametric CAD models. It brings model preparation, visualisation, variant history and engineering exports into one internal design environment.",
            "offeringBoundaries": [
              "Forge is an internal project, not a publicly available design subscription.",
              "Documentation supports CAD, versions and exports; it does not establish a live connection to a physical printer.",
              "Exported geometry needs qualified engineering and manufacturing checks."
            ]
          },
          "readiness": {
            "commercialStatus": "internal-only",
            "documentedState": "Forge explores an AI-assisted route to parametric CAD models. It brings model preparation, visualisation, variant history and engineering exports into one internal design environment.",
            "notEstablished": [
              "Forge is an internal project, not a publicly available design subscription.",
              "Documentation supports CAD, versions and exports; it does not establish a live connection to a physical printer.",
              "Exported geometry needs qualified engineering and manufacturing checks."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "Forge explores an AI-assisted route to parametric CAD models. It brings model preparation, visualisation, variant history and engineering exports into one internal design environment."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Teams exploring AI-assisted engineering workflows",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Teams exploring AI-assisted engineering workflows"
              ],
              "pains": [
                "Moving between a design idea, its geometry and the next revision can create repeated manual work. A shared history and export workflow help make design iteration more organised."
              ],
              "triggers": [
                "When you want to assess AI assistance for a bounded modelling task or the handover from design to manufacturing preparation."
              ],
              "fitConditions": [
                "A bounded design brief, dimensions and intended output",
                "A qualified reviewer for geometry and manufacturing requirements"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Designers assessing parametric modelling and variants",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Designers assessing parametric modelling and variants"
              ],
              "pains": [
                "Moving between a design idea, its geometry and the next revision can create repeated manual work. A shared history and export workflow help make design iteration more organised."
              ],
              "triggers": [
                "When you want to assess AI assistance for a bounded modelling task or the handover from design to manufacturing preparation."
              ],
              "fitConditions": [
                "A bounded design brief, dimensions and intended output",
                "A qualified reviewer for geometry and manufacturing requirements"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Businesses connecting software with prototyping",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Businesses connecting software with prototyping"
              ],
              "pains": [
                "Moving between a design idea, its geometry and the next revision can create repeated manual work. A shared history and export workflow help make design iteration more organised."
              ],
              "triggers": [
                "When you want to assess AI assistance for a bounded modelling task or the handover from design to manufacturing preparation."
              ],
              "fitConditions": [
                "A bounded design brief, dimensions and intended output",
                "A qualified reviewer for geometry and manufacturing requirements"
              ]
            }
          ],
          "systemModel": {
            "principle": "Forge explores an AI-assisted route to parametric CAD models. It brings model preparation, visualisation, variant history and engineering exports into one internal design environment.",
            "components": [
              {
                "id": "component-1",
                "name": "Parametric modelling",
                "purpose": "Work with model parameters and editable design variations.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Visualisation",
                "purpose": "Review the proposed geometry in the design environment.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Version history",
                "purpose": "Keep track of variants and changes during iteration.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Engineering exports",
                "purpose": "Prepare STEP, STL and 3MF files for the next engineering or print-preparation step.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "A bounded design brief, dimensions and intended output",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "A qualified reviewer for geometry and manufacturing requirements",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "Reviewed design variants within the internal or agreed pilot scope",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "STEP, STL or 3MF files for downstream preparation",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Define a modelling task",
                "description": "Agree the geometry, parameters and intended use.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree the geometry, parameters and intended use."
                ],
                "outputNames": [
                  "Define a modelling task"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Prepare and inspect a model",
                "description": "Review the generated or edited design rather than assuming it is correct.",
                "customerContribution": [],
                "providerContribution": [
                  "Review the generated or edited design rather than assuming it is correct."
                ],
                "outputNames": [
                  "Prepare and inspect a model"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Refine a variant",
                "description": "Adjust parameters and compare the resulting versions.",
                "customerContribution": [],
                "providerContribution": [
                  "Adjust parameters and compare the resulting versions."
                ],
                "outputNames": [
                  "Refine a variant"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Export for the next tool",
                "description": "Check the required file format and downstream engineering work.",
                "customerContribution": [],
                "providerContribution": [
                  "Check the required file format and downstream engineering work."
                ],
                "outputNames": [
                  "Export for the next tool"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "A separately scoped discussion or evaluation; access is not implied."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "A bounded design brief, dimensions and intended output",
              "A qualified reviewer for geometry and manufacturing requirements"
            ],
            "customerResponsibilities": [
              "A bounded design brief, dimensions and intended output",
              "A qualified reviewer for geometry and manufacturing requirements"
            ],
            "providerResponsibilities": [
              "Reviewed design variants within the internal or agreed pilot scope",
              "STEP, STL or 3MF files for downstream preparation"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Forge is an internal project, not a publicly available design subscription.",
              "Documentation supports CAD, versions and exports; it does not establish a live connection to a physical printer.",
              "Exported geometry needs qualified engineering and manufacturing checks."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "CAD and print-preparation tools",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Use exported files in a compatible downstream tool and check the resulting model there.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "A more organised design iteration workflow",
              "mechanism": "Moving between a design idea, its geometry and the next revision can create repeated manual work. A shared history and export workflow help make design iteration more organised.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Visible variants and a clearer handover to downstream tools",
              "mechanism": "Moving between a design idea, its geometry and the next revision can create repeated manual work. A shared history and export workflow help make design iteration more organised.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Practical experience for assessing AI-assisted CAD",
              "mechanism": "Moving between a design idea, its geometry and the next revision can create repeated manual work. A shared history and export workflow help make design iteration more organised.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When you want to assess AI assistance for a bounded modelling task or the handover from design to manufacturing preparation."
            ],
            "poorFitSignals": [
              "Forge is an internal project, not a publicly available design subscription.",
              "Documentation supports CAD, versions and exports; it does not establish a live connection to a physical printer.",
              "Exported geometry needs qualified engineering and manufacturing checks."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Forge is an internal project, not a publicly available design subscription.",
              "Documentation supports CAD, versions and exports; it does not establish a live connection to a physical printer.",
              "Exported geometry needs qualified engineering and manufacturing checks."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Does Forge directly operate a 3D printer?",
              "answer": "That is not established by the reviewed documentation. The documented scope includes CAD, version history and exports for later preparation.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Are exported models ready for manufacturing?",
              "answer": "They require the engineering, tolerancing and manufacturing checks appropriate to the intended use.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/forge-ai-parametric-3d-design/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "hardware",
        "name": "Hardware development and manufacturing",
        "brand": "LIVE4K",
        "kind": "service",
        "availability": "by-arrangement",
        "website": "https://live4k.media/",
        "summary": "Custom hardware from mechanical 3D design and electronics through prototyping and manufacturing to software integration and controls.",
        "what": "We connect mechanical design, electronics and software when creating a physical device. Work can run from an initial concept through a prototype to an agreed manufacturing and operating setup.",
        "why": "A device only works as a whole when its enclosure, electronics, firmware or application and controls fit together. Developing those relationships together helps expose practical constraints earlier.",
        "who": [
          "Businesses needing a purpose-built device",
          "Teams developing monitoring or control equipment",
          "Projects that connect physical processes with software"
        ],
        "where": "In development and prototyping environments, followed by the agreed manufacturing or installation context.",
        "when": "When a standard device does not fit your process, or an idea needs a practical prototype and a route to further development.",
        "how": [
          "Agree the environment, function and intended users.",
          "Plan mechanics, electronics, software and their interfaces.",
          "Check the agreed functions and identify changes.",
          "Agree further development, manufacturing and operating responsibilities."
        ],
        "differentiators": [
          "Hardware and software development are part of the same team’s work.",
          "Our own lighting and monitoring projects provide practical implementation experience."
        ],
        "benefits": [
          "A coordinated design across physical and digital parts",
          "A practical way to assess an idea through prototyping",
          "Controls and data considered alongside the device itself"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Mechanical 3D design",
            "description": "Prepare the physical design around the intended use and assembly.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Electronics",
            "description": "Develop the electronic part within the agreed scope.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Prototyping and manufacturing",
            "description": "Move from an initial prototype towards an explicitly defined production step.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Software and controls",
            "description": "Connect the device to the required application, interface or operating workflow.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Industrial and service businesses",
            "need": "Connect a physical process to an application",
            "solution": "Design the device, data path and controls together.",
            "expectedBenefit": "A more coherent physical-to-digital workflow."
          },
          {
            "audience": "Product teams",
            "need": "Test an idea before the next investment",
            "solution": "Build a scoped prototype and evaluate agreed functions.",
            "expectedBenefit": "Evidence for the next design decision."
          }
        ],
        "limitations": [
          "Certification, compliance testing, environmental ratings and production quantities require a separate agreement.",
          "A prototype is not automatically a certified serial product.",
          "Component availability, manufacturing methods and installation constraints affect the scope."
        ],
        "tags": [
          "Hardware development and manufacturing",
          "hardware",
          "custom-software",
          "digital-fabrication"
        ],
        "relatedProjectIds": [
          "software",
          "forge",
          "lighting",
          "water-sight",
          "simroom"
        ],
        "details": {
          "aliases": [
            "Hardware development and manufacturing",
            "Custom hardware development and manufacturing"
          ],
          "domainIds": [
            "hardware",
            "custom-software",
            "digital-fabrication"
          ],
          "positioning": {
            "category": "Custom hardware development and manufacturing",
            "elevatorPitch": "Custom hardware from mechanical 3D design and electronics through prototyping and manufacturing to software integration and controls.",
            "marketRole": "We connect mechanical design, electronics and software when creating a physical device. Work can run from an initial concept through a prototype to an agreed manufacturing and operating setup.",
            "offeringBoundaries": [
              "Certification, compliance testing, environmental ratings and production quantities require a separate agreement.",
              "A prototype is not automatically a certified serial product.",
              "Component availability, manufacturing methods and installation constraints affect the scope."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "We connect mechanical design, electronics and software when creating a physical device. Work can run from an initial concept through a prototype to an agreed manufacturing and operating setup.",
            "notEstablished": [
              "Certification, compliance testing, environmental ratings and production quantities require a separate agreement.",
              "A prototype is not automatically a certified serial product.",
              "Component availability, manufacturing methods and installation constraints affect the scope."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "We connect mechanical design, electronics and software when creating a physical device. Work can run from an initial concept through a prototype to an agreed manufacturing and operating setup."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Businesses needing a purpose-built device",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Businesses needing a purpose-built device"
              ],
              "pains": [
                "A device only works as a whole when its enclosure, electronics, firmware or application and controls fit together. Developing those relationships together helps expose practical constraints earlier."
              ],
              "triggers": [
                "When a standard device does not fit your process, or an idea needs a practical prototype and a route to further development."
              ],
              "fitConditions": [
                "A concrete use case, operating environment and functional priorities",
                "Agreed acceptance criteria and access to the relevant process or installation"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Teams developing monitoring or control equipment",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Teams developing monitoring or control equipment"
              ],
              "pains": [
                "A device only works as a whole when its enclosure, electronics, firmware or application and controls fit together. Developing those relationships together helps expose practical constraints earlier."
              ],
              "triggers": [
                "When a standard device does not fit your process, or an idea needs a practical prototype and a route to further development."
              ],
              "fitConditions": [
                "A concrete use case, operating environment and functional priorities",
                "Agreed acceptance criteria and access to the relevant process or installation"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Projects that connect physical processes with software",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Projects that connect physical processes with software"
              ],
              "pains": [
                "A device only works as a whole when its enclosure, electronics, firmware or application and controls fit together. Developing those relationships together helps expose practical constraints earlier."
              ],
              "triggers": [
                "When a standard device does not fit your process, or an idea needs a practical prototype and a route to further development."
              ],
              "fitConditions": [
                "A concrete use case, operating environment and functional priorities",
                "Agreed acceptance criteria and access to the relevant process or installation"
              ]
            }
          ],
          "systemModel": {
            "principle": "We connect mechanical design, electronics and software when creating a physical device. Work can run from an initial concept through a prototype to an agreed manufacturing and operating setup.",
            "components": [
              {
                "id": "component-1",
                "name": "Mechanical 3D design",
                "purpose": "Prepare the physical design around the intended use and assembly.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Electronics",
                "purpose": "Develop the electronic part within the agreed scope.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Prototyping and manufacturing",
                "purpose": "Move from an initial prototype towards an explicitly defined production step.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Software and controls",
                "purpose": "Connect the device to the required application, interface or operating workflow.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "A concrete use case, operating environment and functional priorities",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Agreed acceptance criteria and access to the relevant process or installation",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "Design and prototype deliverables within scope",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Agreed manufacturing, integration or operating preparation",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Define use and constraints",
                "description": "Agree the environment, function and intended users.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree the environment, function and intended users."
                ],
                "outputNames": [
                  "Define use and constraints"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Design the parts",
                "description": "Plan mechanics, electronics, software and their interfaces.",
                "customerContribution": [],
                "providerContribution": [
                  "Plan mechanics, electronics, software and their interfaces."
                ],
                "outputNames": [
                  "Design the parts"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Build and assess a prototype",
                "description": "Check the agreed functions and identify changes.",
                "customerContribution": [],
                "providerContribution": [
                  "Check the agreed functions and identify changes."
                ],
                "outputNames": [
                  "Build and assess a prototype"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Prepare the next stage",
                "description": "Agree further development, manufacturing and operating responsibilities.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree further development, manufacturing and operating responsibilities."
                ],
                "outputNames": [
                  "Prepare the next stage"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "A concrete use case, operating environment and functional priorities",
              "Agreed acceptance criteria and access to the relevant process or installation"
            ],
            "customerResponsibilities": [
              "A concrete use case, operating environment and functional priorities",
              "Agreed acceptance criteria and access to the relevant process or installation"
            ],
            "providerResponsibilities": [
              "Design and prototype deliverables within scope",
              "Agreed manufacturing, integration or operating preparation"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Certification, compliance testing, environmental ratings and production quantities require a separate agreement.",
              "A prototype is not automatically a certified serial product.",
              "Component availability, manufacturing methods and installation constraints affect the scope."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Software applications",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Define the data, control interface and operating responsibilities for the device.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "id": "integration-2",
              "name": "Existing equipment",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Check electrical, mechanical and protocol compatibility for the specific connection.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "A coordinated design across physical and digital parts",
              "mechanism": "A device only works as a whole when its enclosure, electronics, firmware or application and controls fit together. Developing those relationships together helps expose practical constraints earlier.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "A practical way to assess an idea through prototyping",
              "mechanism": "A device only works as a whole when its enclosure, electronics, firmware or application and controls fit together. Developing those relationships together helps expose practical constraints earlier.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Controls and data considered alongside the device itself",
              "mechanism": "A device only works as a whole when its enclosure, electronics, firmware or application and controls fit together. Developing those relationships together helps expose practical constraints earlier.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When a standard device does not fit your process, or an idea needs a practical prototype and a route to further development."
            ],
            "poorFitSignals": [
              "Certification, compliance testing, environmental ratings and production quantities require a separate agreement.",
              "A prototype is not automatically a certified serial product.",
              "Component availability, manufacturing methods and installation constraints affect the scope."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Certification, compliance testing, environmental ratings and production quantities require a separate agreement.",
              "A prototype is not automatically a certified serial product.",
              "Component availability, manufacturing methods and installation constraints affect the scope."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Can you also build the software?",
              "answer": "Yes, software and controls can be designed with the hardware as part of the agreed project.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Does a prototype include certification?",
              "answer": "Not automatically. Required standards, testing and certification responsibilities must be included explicitly.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/custom-hardware-development-manufacturing/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "infrastructure",
        "name": "Networks, servers and private cloud",
        "brand": "LIVE4K",
        "kind": "service",
        "availability": "by-arrangement",
        "website": "https://live4k.media/",
        "summary": "Design, deployment and management of private networks, Linux servers and a Kubernetes-based business cloud, with operational monitoring.",
        "what": "We prepare the infrastructure that business applications and data need. Networks, Linux servers and Kubernetes are considered as parts of one operating environment with defined management responsibilities.",
        "why": "Applications depend on the systems around them. Designing connectivity, hosting and operational oversight together helps avoid gaps between deployment and everyday use.",
        "who": [
          "Businesses running their own applications",
          "Teams with private server or cloud requirements",
          "Organisations connecting sites, services and operational responsibilities"
        ],
        "where": "In the agreed company, server or hosting environment. On-site installation and remote management depend on the project.",
        "when": "When you are building or changing infrastructure, deploying an application or clarifying who manages the systems it relies on.",
        "how": [
          "Identify sites, applications, data and operational needs.",
          "Agree architecture, access, responsibilities and implementation steps.",
          "Check connectivity and the required service functions.",
          "Define monitoring, maintenance and the response process."
        ],
        "differentiators": [
          "Our software and hardware work informs infrastructure decisions.",
          "Networks, servers and application hosting can be planned together."
        ],
        "benefits": [
          "Infrastructure designed around the applications it supports",
          "Clearer responsibilities for everyday operation",
          "A connection between software delivery and its technical foundations"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Network design and deployment",
            "description": "Prepare connectivity around the actual sites, users and applications.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Linux servers",
            "description": "Set up and manage agreed Linux-based services and their operating environment.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Kubernetes-based cloud",
            "description": "Design a private application platform where this operating model fits the requirements.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Operational monitoring",
            "description": "Include visibility into agreed services as part of the management scope.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Application owners",
            "need": "Prepare a place to run a business system",
            "solution": "Design hosting and network dependencies alongside the application.",
            "expectedBenefit": "A more complete route from development to operation."
          },
          {
            "audience": "Growing businesses",
            "need": "Bring server management into a coherent plan",
            "solution": "Define the environment, monitoring and responsibility for maintenance.",
            "expectedBenefit": "Clearer ownership of everyday operation."
          }
        ],
        "limitations": [
          "Architecture, backup responsibilities, recovery objectives and service levels require explicit agreement.",
          "Kubernetes is an option for suitable workloads, not a requirement for every business.",
          "No universal uptime, capacity or security certification is implied."
        ],
        "tags": [
          "Networks, servers and private cloud",
          "infrastructure",
          "custom-software"
        ],
        "relatedProjectIds": [
          "software",
          "stream",
          "agents"
        ],
        "details": {
          "aliases": [
            "Networks, servers and private cloud",
            "Network and server management, Linux and private cloud"
          ],
          "domainIds": [
            "infrastructure",
            "custom-software"
          ],
          "positioning": {
            "category": "Network and server management, Linux and private cloud",
            "elevatorPitch": "Design, deployment and management of private networks, Linux servers and a Kubernetes-based business cloud, with operational monitoring.",
            "marketRole": "We prepare the infrastructure that business applications and data need. Networks, Linux servers and Kubernetes are considered as parts of one operating environment with defined management responsibilities.",
            "offeringBoundaries": [
              "Architecture, backup responsibilities, recovery objectives and service levels require explicit agreement.",
              "Kubernetes is an option for suitable workloads, not a requirement for every business.",
              "No universal uptime, capacity or security certification is implied."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "We prepare the infrastructure that business applications and data need. Networks, Linux servers and Kubernetes are considered as parts of one operating environment with defined management responsibilities.",
            "notEstablished": [
              "Architecture, backup responsibilities, recovery objectives and service levels require explicit agreement.",
              "Kubernetes is an option for suitable workloads, not a requirement for every business.",
              "No universal uptime, capacity or security certification is implied."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "We prepare the infrastructure that business applications and data need. Networks, Linux servers and Kubernetes are considered as parts of one operating environment with defined management responsibilities."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Businesses running their own applications",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Businesses running their own applications"
              ],
              "pains": [
                "Applications depend on the systems around them. Designing connectivity, hosting and operational oversight together helps avoid gaps between deployment and everyday use."
              ],
              "triggers": [
                "When you are building or changing infrastructure, deploying an application or clarifying who manages the systems it relies on."
              ],
              "fitConditions": [
                "Current infrastructure information and application requirements",
                "Authorised access, change ownership and agreed operating constraints"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Teams with private server or cloud requirements",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Teams with private server or cloud requirements"
              ],
              "pains": [
                "Applications depend on the systems around them. Designing connectivity, hosting and operational oversight together helps avoid gaps between deployment and everyday use."
              ],
              "triggers": [
                "When you are building or changing infrastructure, deploying an application or clarifying who manages the systems it relies on."
              ],
              "fitConditions": [
                "Current infrastructure information and application requirements",
                "Authorised access, change ownership and agreed operating constraints"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Organisations connecting sites, services and operational responsibilities",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Organisations connecting sites, services and operational responsibilities"
              ],
              "pains": [
                "Applications depend on the systems around them. Designing connectivity, hosting and operational oversight together helps avoid gaps between deployment and everyday use."
              ],
              "triggers": [
                "When you are building or changing infrastructure, deploying an application or clarifying who manages the systems it relies on."
              ],
              "fitConditions": [
                "Current infrastructure information and application requirements",
                "Authorised access, change ownership and agreed operating constraints"
              ]
            }
          ],
          "systemModel": {
            "principle": "We prepare the infrastructure that business applications and data need. Networks, Linux servers and Kubernetes are considered as parts of one operating environment with defined management responsibilities.",
            "components": [
              {
                "id": "component-1",
                "name": "Network design and deployment",
                "purpose": "Prepare connectivity around the actual sites, users and applications.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Linux servers",
                "purpose": "Set up and manage agreed Linux-based services and their operating environment.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Kubernetes-based cloud",
                "purpose": "Design a private application platform where this operating model fits the requirements.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Operational monitoring",
                "purpose": "Include visibility into agreed services as part of the management scope.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "Current infrastructure information and application requirements",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Authorised access, change ownership and agreed operating constraints",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "The agreed network, server or cloud environment",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Management and monitoring arrangements defined in the project",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Map the dependencies",
                "description": "Identify sites, applications, data and operational needs.",
                "customerContribution": [],
                "providerContribution": [
                  "Identify sites, applications, data and operational needs."
                ],
                "outputNames": [
                  "Map the dependencies"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Design the environment",
                "description": "Agree architecture, access, responsibilities and implementation steps.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree architecture, access, responsibilities and implementation steps."
                ],
                "outputNames": [
                  "Design the environment"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Deploy and verify",
                "description": "Check connectivity and the required service functions.",
                "customerContribution": [],
                "providerContribution": [
                  "Check connectivity and the required service functions."
                ],
                "outputNames": [
                  "Deploy and verify"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Agree ongoing management",
                "description": "Define monitoring, maintenance and the response process.",
                "customerContribution": [],
                "providerContribution": [
                  "Define monitoring, maintenance and the response process."
                ],
                "outputNames": [
                  "Agree ongoing management"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "Current infrastructure information and application requirements",
              "Authorised access, change ownership and agreed operating constraints"
            ],
            "customerResponsibilities": [
              "Current infrastructure information and application requirements",
              "Authorised access, change ownership and agreed operating constraints"
            ],
            "providerResponsibilities": [
              "The agreed network, server or cloud environment",
              "Management and monitoring arrangements defined in the project"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Architecture, backup responsibilities, recovery objectives and service levels require explicit agreement.",
              "Kubernetes is an option for suitable workloads, not a requirement for every business.",
              "No universal uptime, capacity or security certification is implied."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Business applications",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Match hosting, connectivity and access requirements to the actual application.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "id": "integration-2",
              "name": "Existing infrastructure",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Assess compatibility, dependencies and the transition plan before changes.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "Infrastructure designed around the applications it supports",
              "mechanism": "Applications depend on the systems around them. Designing connectivity, hosting and operational oversight together helps avoid gaps between deployment and everyday use.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Clearer responsibilities for everyday operation",
              "mechanism": "Applications depend on the systems around them. Designing connectivity, hosting and operational oversight together helps avoid gaps between deployment and everyday use.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "A connection between software delivery and its technical foundations",
              "mechanism": "Applications depend on the systems around them. Designing connectivity, hosting and operational oversight together helps avoid gaps between deployment and everyday use.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When you are building or changing infrastructure, deploying an application or clarifying who manages the systems it relies on."
            ],
            "poorFitSignals": [
              "Architecture, backup responsibilities, recovery objectives and service levels require explicit agreement.",
              "Kubernetes is an option for suitable workloads, not a requirement for every business.",
              "No universal uptime, capacity or security certification is implied."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Architecture, backup responsibilities, recovery objectives and service levels require explicit agreement.",
              "Kubernetes is an option for suitable workloads, not a requirement for every business.",
              "No universal uptime, capacity or security certification is implied."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Do we need Kubernetes?",
              "answer": "That depends on your workloads and operating requirements. We assess the fit rather than assume one platform suits every project.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "What does management include?",
              "answer": "The managed services, monitoring, access, maintenance and response responsibilities are defined for your environment.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/network-server-management-private-cloud/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "lighting",
        "name": "LIVE4K Lighting",
        "brand": "LIVE4K",
        "kind": "product",
        "availability": "by-arrangement",
        "website": "https://lighting.live4k.media/",
        "summary": "Colour lighting for large areas using our own RGB modules, individual control of lighting points and a shared lighting direction.",
        "what": "We combine custom RGB modules and control software to create lighting across a space. The behaviour of individual points can be designed around their physical arrangement rather than applying one effect to an entire chain.",
        "why": "A large lighting installation needs the physical layout, electrical arrangement and control logic to work together. Bringing hardware and software into the same design creates room for effects that suit the actual venue.",
        "who": [
          "Event and installation producers",
          "Venues and experiential spaces",
          "AV partners requiring coordinated colour lighting"
        ],
        "where": "Event spaces and installations whose physical, electrical and environmental conditions have been checked for the proposed setup.",
        "when": "When a large area or a spatial arrangement needs individually controlled colour lighting.",
        "how": [
          "Agree the visual intention, placement and installation conditions.",
          "Plan modules, power, wiring and the control approach.",
          "Create and check the required scenes or spatial behaviour.",
          "Test the actual arrangement and agree operation and handover."
        ],
        "differentiators": [
          "We develop both the modules and their control software.",
          "The physical positions of the lighting points inform the effect design."
        ],
        "benefits": [
          "Effects designed for the space",
          "Coordinated hardware and control logic",
          "Lighting that can form part of the event production"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Custom RGB modules",
            "description": "Our own modular lighting hardware for the agreed installation.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Individual point control",
            "description": "Define the behaviour of lighting points within the spatial arrangement.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Spatial effects",
            "description": "Use maps and programmable effects that reflect the layout of the installation.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Lighting direction",
            "description": "Coordinate the installation with the wider AV or lighting control plan as agreed.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Event producers",
            "need": "Give a venue a coherent visual identity",
            "solution": "Design RGB colour scenes around the actual installation layout.",
            "expectedBenefit": "A consistent atmosphere across a larger area."
          },
          {
            "audience": "Installation designers",
            "need": "Control points individually",
            "solution": "Map modules and create behaviour for different parts of the space.",
            "expectedBenefit": "More flexibility than a single effect for the whole installation."
          }
        ],
        "limitations": [
          "Scale, output, mounting and environmental suitability must be checked per installation.",
          "Compatibility with a particular console or protocol requires confirmation.",
          "No universal brightness, outdoor rating or capacity is implied by the portfolio description."
        ],
        "tags": [
          "LIVE4K Lighting",
          "lighting",
          "hardware",
          "event-production"
        ],
        "relatedProjectIds": [
          "events",
          "hardware",
          "agents"
        ],
        "details": {
          "aliases": [
            "LIVE4K Lighting",
            "LIVE4K Lighting: large-area RGB lighting"
          ],
          "domainIds": [
            "lighting",
            "hardware",
            "event-production"
          ],
          "positioning": {
            "category": "LIVE4K Lighting: large-area RGB lighting",
            "elevatorPitch": "Colour lighting for large areas using our own RGB modules, individual control of lighting points and a shared lighting direction.",
            "marketRole": "We combine custom RGB modules and control software to create lighting across a space. The behaviour of individual points can be designed around their physical arrangement rather than applying one effect to an entire chain.",
            "offeringBoundaries": [
              "Scale, output, mounting and environmental suitability must be checked per installation.",
              "Compatibility with a particular console or protocol requires confirmation.",
              "No universal brightness, outdoor rating or capacity is implied by the portfolio description."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "We combine custom RGB modules and control software to create lighting across a space. The behaviour of individual points can be designed around their physical arrangement rather than applying one effect to an entire chain.",
            "notEstablished": [
              "Scale, output, mounting and environmental suitability must be checked per installation.",
              "Compatibility with a particular console or protocol requires confirmation.",
              "No universal brightness, outdoor rating or capacity is implied by the portfolio description."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "We combine custom RGB modules and control software to create lighting across a space. The behaviour of individual points can be designed around their physical arrangement rather than applying one effect to an entire chain."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Event and installation producers",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Event and installation producers"
              ],
              "pains": [
                "A large lighting installation needs the physical layout, electrical arrangement and control logic to work together. Bringing hardware and software into the same design creates room for effects that suit the actual venue."
              ],
              "triggers": [
                "When a large area or a spatial arrangement needs individually controlled colour lighting."
              ],
              "fitConditions": [
                "Layout, mounting options, power and environmental conditions",
                "Desired scenes, operating method and production schedule"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Venues and experiential spaces",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Venues and experiential spaces"
              ],
              "pains": [
                "A large lighting installation needs the physical layout, electrical arrangement and control logic to work together. Bringing hardware and software into the same design creates room for effects that suit the actual venue."
              ],
              "triggers": [
                "When a large area or a spatial arrangement needs individually controlled colour lighting."
              ],
              "fitConditions": [
                "Layout, mounting options, power and environmental conditions",
                "Desired scenes, operating method and production schedule"
              ]
            },
            {
              "id": "audience-3",
              "segment": "AV partners requiring coordinated colour lighting",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "AV partners requiring coordinated colour lighting"
              ],
              "pains": [
                "A large lighting installation needs the physical layout, electrical arrangement and control logic to work together. Bringing hardware and software into the same design creates room for effects that suit the actual venue."
              ],
              "triggers": [
                "When a large area or a spatial arrangement needs individually controlled colour lighting."
              ],
              "fitConditions": [
                "Layout, mounting options, power and environmental conditions",
                "Desired scenes, operating method and production schedule"
              ]
            }
          ],
          "systemModel": {
            "principle": "We combine custom RGB modules and control software to create lighting across a space. The behaviour of individual points can be designed around their physical arrangement rather than applying one effect to an entire chain.",
            "components": [
              {
                "id": "component-1",
                "name": "Custom RGB modules",
                "purpose": "Our own modular lighting hardware for the agreed installation.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Individual point control",
                "purpose": "Define the behaviour of lighting points within the spatial arrangement.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Spatial effects",
                "purpose": "Use maps and programmable effects that reflect the layout of the installation.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Lighting direction",
                "purpose": "Coordinate the installation with the wider AV or lighting control plan as agreed.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "Layout, mounting options, power and environmental conditions",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Desired scenes, operating method and production schedule",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "An agreed lighting arrangement and control setup",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Configured scenes and operating instructions within scope",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Map the space",
                "description": "Agree the visual intention, placement and installation conditions.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree the visual intention, placement and installation conditions."
                ],
                "outputNames": [
                  "Map the space"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Design the system",
                "description": "Plan modules, power, wiring and the control approach.",
                "customerContribution": [],
                "providerContribution": [
                  "Plan modules, power, wiring and the control approach."
                ],
                "outputNames": [
                  "Design the system"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Prepare effects",
                "description": "Create and check the required scenes or spatial behaviour.",
                "customerContribution": [],
                "providerContribution": [
                  "Create and check the required scenes or spatial behaviour."
                ],
                "outputNames": [
                  "Prepare effects"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Install and operate",
                "description": "Test the actual arrangement and agree operation and handover.",
                "customerContribution": [],
                "providerContribution": [
                  "Test the actual arrangement and agree operation and handover."
                ],
                "outputNames": [
                  "Install and operate"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "Layout, mounting options, power and environmental conditions",
              "Desired scenes, operating method and production schedule"
            ],
            "customerResponsibilities": [
              "Layout, mounting options, power and environmental conditions",
              "Desired scenes, operating method and production schedule"
            ],
            "providerResponsibilities": [
              "An agreed lighting arrangement and control setup",
              "Configured scenes and operating instructions within scope"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Scale, output, mounting and environmental suitability must be checked per installation.",
              "Compatibility with a particular console or protocol requires confirmation.",
              "No universal brightness, outdoor rating or capacity is implied by the portfolio description."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "AV and lighting direction",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Coordinate triggers and control interfaces after checking the actual equipment and supported connection method.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "Effects designed for the space",
              "mechanism": "A large lighting installation needs the physical layout, electrical arrangement and control logic to work together. Bringing hardware and software into the same design creates room for effects that suit the actual venue.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Coordinated hardware and control logic",
              "mechanism": "A large lighting installation needs the physical layout, electrical arrangement and control logic to work together. Bringing hardware and software into the same design creates room for effects that suit the actual venue.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Lighting that can form part of the event production",
              "mechanism": "A large lighting installation needs the physical layout, electrical arrangement and control logic to work together. Bringing hardware and software into the same design creates room for effects that suit the actual venue.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When a large area or a spatial arrangement needs individually controlled colour lighting."
            ],
            "poorFitSignals": [
              "Scale, output, mounting and environmental suitability must be checked per installation.",
              "Compatibility with a particular console or protocol requires confirmation.",
              "No universal brightness, outdoor rating or capacity is implied by the portfolio description."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Scale, output, mounting and environmental suitability must be checked per installation.",
              "Compatibility with a particular console or protocol requires confirmation.",
              "No universal brightness, outdoor rating or capacity is implied by the portfolio description."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Can each point behave differently?",
              "answer": "Individual control is part of the concept. The exact arrangement and control capabilities depend on the proposed installation.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Will it connect to our lighting console?",
              "answer": "We need to check the console, control method and agreed integration before confirming compatibility.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/large-area-rgb-lighting/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "podcasts",
        "name": "Videopodcasts and interviews",
        "brand": "LIVE4K",
        "kind": "service",
        "availability": "by-arrangement",
        "website": "https://live4k.media/",
        "summary": "B2B videopodcasts and interviews produced in authentic settings. You arrange the guests; LIVE4K handles preparation, equipment, filming and post-production.",
        "what": "We turn business expertise and conversations into filmed interviews or a coherent series. The technical setup adapts to an authentic location rather than requiring every guest to visit a permanent studio.",
        "why": "Your team knows its subject and guests, but may not have the production capacity to record good picture and sound. A coordinated filming day turns that expertise into content without building an in-house production operation.",
        "who": [
          "Businesses communicating expertise and trust",
          "PR and content agencies",
          "Marketing teams planning interviews with partners or customers"
        ],
        "where": "At company premises, suitable indoor locations or outdoors where the conditions allow a reliable recording.",
        "when": "When you have expert guests, a recurring subject or a series of partner conversations to share with a B2B audience.",
        "how": [
          "Define the subject, audience and shape of the interviews.",
          "You arrange the guests; we plan the technical setup and schedule.",
          "Capture picture and sound in the agreed setting.",
          "Approve the agreed episodes and any separately commissioned derived materials."
        ],
        "differentiators": [
          "Recording in environments that support the story.",
          "Production can connect to conferences, business events and wider company content."
        ],
        "benefits": [
          "Professional recording without operating your own studio",
          "Consistent production across a planned series",
          "More time for your team to focus on the conversation"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Location-based recording",
            "description": "A mobile camera and sound setup chosen for the agreed setting.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Production preparation",
            "description": "Coordinate technical requirements and organise filming days around available guests.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Post-production",
            "description": "Edit the recorded interviews and prepare the agreed final versions.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Expert businesses",
            "need": "Share knowledge that stays inside the company",
            "solution": "Record conversations with specialists in a setting relevant to their work.",
            "expectedBenefit": "An accessible way to explain experience and expertise."
          },
          {
            "audience": "Agencies",
            "need": "Produce a series outside a permanent studio",
            "solution": "Coordinate several guests and a shared filming day at a client location.",
            "expectedBenefit": "A consistent technical and editorial handover."
          }
        ],
        "limitations": [
          "This offering is focused on B2B content.",
          "The customer arranges the guests.",
          "Editorial development, hosting, publication and short clips require an explicit scope agreement."
        ],
        "tags": [
          "Videopodcasts and interviews",
          "digital-content"
        ],
        "relatedProjectIds": [
          "digi-production",
          "events"
        ],
        "details": {
          "aliases": [
            "Videopodcasts and interviews",
            "Videopodcast and interview production"
          ],
          "domainIds": [
            "digital-content"
          ],
          "positioning": {
            "category": "Videopodcast and interview production",
            "elevatorPitch": "B2B videopodcasts and interviews produced in authentic settings. You arrange the guests; LIVE4K handles preparation, equipment, filming and post-production.",
            "marketRole": "We turn business expertise and conversations into filmed interviews or a coherent series. The technical setup adapts to an authentic location rather than requiring every guest to visit a permanent studio.",
            "offeringBoundaries": [
              "This offering is focused on B2B content.",
              "The customer arranges the guests.",
              "Editorial development, hosting, publication and short clips require an explicit scope agreement."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "We turn business expertise and conversations into filmed interviews or a coherent series. The technical setup adapts to an authentic location rather than requiring every guest to visit a permanent studio.",
            "notEstablished": [
              "This offering is focused on B2B content.",
              "The customer arranges the guests.",
              "Editorial development, hosting, publication and short clips require an explicit scope agreement."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "We turn business expertise and conversations into filmed interviews or a coherent series. The technical setup adapts to an authentic location rather than requiring every guest to visit a permanent studio."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Businesses communicating expertise and trust",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Businesses communicating expertise and trust"
              ],
              "pains": [
                "Your team knows its subject and guests, but may not have the production capacity to record good picture and sound. A coordinated filming day turns that expertise into content without building an in-house production operation."
              ],
              "triggers": [
                "When you have expert guests, a recurring subject or a series of partner conversations to share with a B2B audience."
              ],
              "fitConditions": [
                "Relevant topics, available guests and an agreed location",
                "A contact responsible for scheduling and editorial approval"
              ]
            },
            {
              "id": "audience-2",
              "segment": "PR and content agencies",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "PR and content agencies"
              ],
              "pains": [
                "Your team knows its subject and guests, but may not have the production capacity to record good picture and sound. A coordinated filming day turns that expertise into content without building an in-house production operation."
              ],
              "triggers": [
                "When you have expert guests, a recurring subject or a series of partner conversations to share with a B2B audience."
              ],
              "fitConditions": [
                "Relevant topics, available guests and an agreed location",
                "A contact responsible for scheduling and editorial approval"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Marketing teams planning interviews with partners or customers",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Marketing teams planning interviews with partners or customers"
              ],
              "pains": [
                "Your team knows its subject and guests, but may not have the production capacity to record good picture and sound. A coordinated filming day turns that expertise into content without building an in-house production operation."
              ],
              "triggers": [
                "When you have expert guests, a recurring subject or a series of partner conversations to share with a B2B audience."
              ],
              "fitConditions": [
                "Relevant topics, available guests and an agreed location",
                "A contact responsible for scheduling and editorial approval"
              ]
            }
          ],
          "systemModel": {
            "principle": "We turn business expertise and conversations into filmed interviews or a coherent series. The technical setup adapts to an authentic location rather than requiring every guest to visit a permanent studio.",
            "components": [
              {
                "id": "component-1",
                "name": "Location-based recording",
                "purpose": "A mobile camera and sound setup chosen for the agreed setting.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Production preparation",
                "purpose": "Coordinate technical requirements and organise filming days around available guests.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Post-production",
                "purpose": "Edit the recorded interviews and prepare the agreed final versions.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "Relevant topics, available guests and an agreed location",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "A contact responsible for scheduling and editorial approval",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "Edited interviews or episodes",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Additional versions and communication materials within the agreed brief",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Choose the format",
                "description": "Define the subject, audience and shape of the interviews.",
                "customerContribution": [],
                "providerContribution": [
                  "Define the subject, audience and shape of the interviews."
                ],
                "outputNames": [
                  "Choose the format"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Coordinate guests and location",
                "description": "You arrange the guests; we plan the technical setup and schedule.",
                "customerContribution": [],
                "providerContribution": [
                  "You arrange the guests; we plan the technical setup and schedule."
                ],
                "outputNames": [
                  "Coordinate guests and location"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Record the conversations",
                "description": "Capture picture and sound in the agreed setting.",
                "customerContribution": [],
                "providerContribution": [
                  "Capture picture and sound in the agreed setting."
                ],
                "outputNames": [
                  "Record the conversations"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Review the edits",
                "description": "Approve the agreed episodes and any separately commissioned derived materials.",
                "customerContribution": [],
                "providerContribution": [
                  "Approve the agreed episodes and any separately commissioned derived materials."
                ],
                "outputNames": [
                  "Review the edits"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "Relevant topics, available guests and an agreed location",
              "A contact responsible for scheduling and editorial approval"
            ],
            "customerResponsibilities": [
              "Relevant topics, available guests and an agreed location",
              "A contact responsible for scheduling and editorial approval"
            ],
            "providerResponsibilities": [
              "Edited interviews or episodes",
              "Additional versions and communication materials within the agreed brief"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "This offering is focused on B2B content.",
              "The customer arranges the guests.",
              "Editorial development, hosting, publication and short clips require an explicit scope agreement."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Company communication",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Prepare final files for your website, internal communication or publishing workflow.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "Professional recording without operating your own studio",
              "mechanism": "Your team knows its subject and guests, but may not have the production capacity to record good picture and sound. A coordinated filming day turns that expertise into content without building an in-house production operation.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Consistent production across a planned series",
              "mechanism": "Your team knows its subject and guests, but may not have the production capacity to record good picture and sound. A coordinated filming day turns that expertise into content without building an in-house production operation.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "More time for your team to focus on the conversation",
              "mechanism": "Your team knows its subject and guests, but may not have the production capacity to record good picture and sound. A coordinated filming day turns that expertise into content without building an in-house production operation.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When you have expert guests, a recurring subject or a series of partner conversations to share with a B2B audience."
            ],
            "poorFitSignals": [
              "This offering is focused on B2B content.",
              "The customer arranges the guests.",
              "Editorial development, hosting, publication and short clips require an explicit scope agreement."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "This offering is focused on B2B content.",
              "The customer arranges the guests.",
              "Editorial development, hosting, publication and short clips require an explicit scope agreement."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Do we need our own studio?",
              "answer": "No. We can prepare a mobile production at your location or another suitable setting after checking the technical conditions.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Who arranges the guests?",
              "answer": "You arrange the guests and their availability. We coordinate the filming plan and technical production.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/videopodcast-interview-production/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "remarketagent",
        "name": "RemarketAgent",
        "brand": "LIVE4K",
        "kind": "product",
        "availability": "in-development",
        "website": "https://remarketagent.com/",
        "summary": "An AI workflow in development for preparing business equipment for resale: photos and QR identification, item recognition, a reviewed sales plan and subsequent steps for supported marketplaces.",
        "what": "RemarketAgent explores the path from a photographed item to a controlled plan for selling unused equipment. It connects identification and preparation work while keeping later marketplace actions as explicitly verified steps.",
        "why": "Unused business equipment can remain in storage because identifying it and preparing a sale takes time. A structured preparation workflow may reduce that friction without assuming every marketplace action is already automated.",
        "who": [
          "Companies with unused equipment",
          "Operations and asset management teams",
          "Teams exploring a more structured remarketing process"
        ],
        "where": "A development and sandbox context. Production use and marketplace connections require separate validation.",
        "when": "When you want to assess how to turn a backlog of equipment into reviewed and actionable resale preparation.",
        "how": [
          "Prepare photographs and the agreed identification reference.",
          "Check the proposed identity, condition and available information.",
          "Review the suggested sales preparation and intended destination.",
          "Confirm which supported actions are actually ready for the selected marketplace."
        ],
        "differentiators": [
          "Connects physical item capture with AI-assisted preparation.",
          "Treats recognition, planning and later sales actions as separate stages."
        ],
        "benefits": [
          "A structured route from storage to resale preparation",
          "A review point before consequential sales actions",
          "A basis for testing a practical remarketing workflow"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Photos and QR identification",
            "description": "Organise item capture and identification as the start of a workflow.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Item recognition",
            "description": "Prepare an identification proposal based on available item information.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Sales planning",
            "description": "Prepare a proposed sales plan that can be checked by a person.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Marketplace steps",
            "description": "Explore subsequent actions for supported marketplaces within a verified scope.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Operations teams",
            "need": "Make a backlog of unused assets actionable",
            "solution": "Test a photo-to-plan workflow with a limited set of equipment.",
            "expectedBenefit": "A clearer view of the preparation work needed."
          },
          {
            "audience": "Asset managers",
            "need": "Review sales proposals consistently",
            "solution": "Keep identification and plan approval as explicit stages.",
            "expectedBenefit": "More traceable decisions before marketplace action."
          }
        ],
        "limitations": [
          "This project is in development and is not presented as a finished production resale service.",
          "A working sandbox is not evidence of completed live sales, payments or eBay transactions.",
          "Valuation, ownership, condition, account access and marketplace readiness require verification."
        ],
        "tags": [
          "RemarketAgent",
          "remarketing",
          "ai-workforce"
        ],
        "relatedProjectIds": [
          "agents",
          "software"
        ],
        "details": {
          "aliases": [
            "RemarketAgent",
            "RemarketAgent: AI-assisted business equipment resale preparation"
          ],
          "domainIds": [
            "remarketing",
            "ai-workforce"
          ],
          "positioning": {
            "category": "RemarketAgent: AI-assisted business equipment resale preparation",
            "elevatorPitch": "An AI workflow in development for preparing business equipment for resale: photos and QR identification, item recognition, a reviewed sales plan and subsequent steps for supported marketplaces.",
            "marketRole": "RemarketAgent explores the path from a photographed item to a controlled plan for selling unused equipment. It connects identification and preparation work while keeping later marketplace actions as explicitly verified steps.",
            "offeringBoundaries": [
              "This project is in development and is not presented as a finished production resale service.",
              "A working sandbox is not evidence of completed live sales, payments or eBay transactions.",
              "Valuation, ownership, condition, account access and marketplace readiness require verification."
            ]
          },
          "readiness": {
            "commercialStatus": "development-preview",
            "documentedState": "RemarketAgent explores the path from a photographed item to a controlled plan for selling unused equipment. It connects identification and preparation work while keeping later marketplace actions as explicitly verified steps.",
            "notEstablished": [
              "This project is in development and is not presented as a finished production resale service.",
              "A working sandbox is not evidence of completed live sales, payments or eBay transactions.",
              "Valuation, ownership, condition, account access and marketplace readiness require verification."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "RemarketAgent explores the path from a photographed item to a controlled plan for selling unused equipment. It connects identification and preparation work while keeping later marketplace actions as explicitly verified steps."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Companies with unused equipment",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Companies with unused equipment"
              ],
              "pains": [
                "Unused business equipment can remain in storage because identifying it and preparing a sale takes time. A structured preparation workflow may reduce that friction without assuming every marketplace action is already automated."
              ],
              "triggers": [
                "When you want to assess how to turn a backlog of equipment into reviewed and actionable resale preparation."
              ],
              "fitConditions": [
                "Representative items, photographs and available asset information",
                "A person who can verify identification, ownership, condition and any sales proposal"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Operations and asset management teams",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Operations and asset management teams"
              ],
              "pains": [
                "Unused business equipment can remain in storage because identifying it and preparing a sale takes time. A structured preparation workflow may reduce that friction without assuming every marketplace action is already automated."
              ],
              "triggers": [
                "When you want to assess how to turn a backlog of equipment into reviewed and actionable resale preparation."
              ],
              "fitConditions": [
                "Representative items, photographs and available asset information",
                "A person who can verify identification, ownership, condition and any sales proposal"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Teams exploring a more structured remarketing process",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Teams exploring a more structured remarketing process"
              ],
              "pains": [
                "Unused business equipment can remain in storage because identifying it and preparing a sale takes time. A structured preparation workflow may reduce that friction without assuming every marketplace action is already automated."
              ],
              "triggers": [
                "When you want to assess how to turn a backlog of equipment into reviewed and actionable resale preparation."
              ],
              "fitConditions": [
                "Representative items, photographs and available asset information",
                "A person who can verify identification, ownership, condition and any sales proposal"
              ]
            }
          ],
          "systemModel": {
            "principle": "RemarketAgent explores the path from a photographed item to a controlled plan for selling unused equipment. It connects identification and preparation work while keeping later marketplace actions as explicitly verified steps.",
            "components": [
              {
                "id": "component-1",
                "name": "Photos and QR identification",
                "purpose": "Organise item capture and identification as the start of a workflow.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Item recognition",
                "purpose": "Prepare an identification proposal based on available item information.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Sales planning",
                "purpose": "Prepare a proposed sales plan that can be checked by a person.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Marketplace steps",
                "purpose": "Explore subsequent actions for supported marketplaces within a verified scope.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "Representative items, photographs and available asset information",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "A person who can verify identification, ownership, condition and any sales proposal",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "A reviewed identification and sales preparation proposal",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Findings from a separately agreed development or sandbox evaluation",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Capture an item",
                "description": "Prepare photographs and the agreed identification reference.",
                "customerContribution": [],
                "providerContribution": [
                  "Prepare photographs and the agreed identification reference."
                ],
                "outputNames": [
                  "Capture an item"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Review identification",
                "description": "Check the proposed identity, condition and available information.",
                "customerContribution": [],
                "providerContribution": [
                  "Check the proposed identity, condition and available information."
                ],
                "outputNames": [
                  "Review identification"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Approve a plan",
                "description": "Review the suggested sales preparation and intended destination.",
                "customerContribution": [],
                "providerContribution": [
                  "Review the suggested sales preparation and intended destination."
                ],
                "outputNames": [
                  "Approve a plan"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Validate the next step",
                "description": "Confirm which supported actions are actually ready for the selected marketplace.",
                "customerContribution": [],
                "providerContribution": [
                  "Confirm which supported actions are actually ready for the selected marketplace."
                ],
                "outputNames": [
                  "Validate the next step"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "A separately scoped discussion or evaluation; access is not implied."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "Representative items, photographs and available asset information",
              "A person who can verify identification, ownership, condition and any sales proposal"
            ],
            "customerResponsibilities": [
              "Representative items, photographs and available asset information",
              "A person who can verify identification, ownership, condition and any sales proposal"
            ],
            "providerResponsibilities": [
              "A reviewed identification and sales preparation proposal",
              "Findings from a separately agreed development or sandbox evaluation"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "This project is in development and is not presented as a finished production resale service.",
              "A working sandbox is not evidence of completed live sales, payments or eBay transactions.",
              "Valuation, ownership, condition, account access and marketplace readiness require verification."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Supported marketplaces",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Each connector, account permission and subsequent action must be checked independently before production use.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "A structured route from storage to resale preparation",
              "mechanism": "Unused business equipment can remain in storage because identifying it and preparing a sale takes time. A structured preparation workflow may reduce that friction without assuming every marketplace action is already automated.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "A review point before consequential sales actions",
              "mechanism": "Unused business equipment can remain in storage because identifying it and preparing a sale takes time. A structured preparation workflow may reduce that friction without assuming every marketplace action is already automated.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "A basis for testing a practical remarketing workflow",
              "mechanism": "Unused business equipment can remain in storage because identifying it and preparing a sale takes time. A structured preparation workflow may reduce that friction without assuming every marketplace action is already automated.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When you want to assess how to turn a backlog of equipment into reviewed and actionable resale preparation."
            ],
            "poorFitSignals": [
              "This project is in development and is not presented as a finished production resale service.",
              "A working sandbox is not evidence of completed live sales, payments or eBay transactions.",
              "Valuation, ownership, condition, account access and marketplace readiness require verification."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "This project is in development and is not presented as a finished production resale service.",
              "A working sandbox is not evidence of completed live sales, payments or eBay transactions.",
              "Valuation, ownership, condition, account access and marketplace readiness require verification."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Is this ready to sell equipment automatically?",
              "answer": "No such general claim is made. The project is in development and later marketplace actions require separate verification.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Does a sandbox result prove live transactions work?",
              "answer": "No. Sandbox behaviour, live marketplace access, completed sales and payments are different things.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/remarketagent-business-equipment-resale/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "simroom",
        "name": "SIMROOM",
        "brand": "LIVE4K",
        "kind": "product",
        "availability": "by-arrangement",
        "website": "https://simroom.cz/",
        "summary": "An AV workflow for simulation training that connects scenarios, cameras, audio, recording, important-moment markers and subsequent debriefing.",
        "what": "SIMROOM supports the path from a training scenario to a review of what happened. Cameras, sound and recording are connected with event markers so instructors can return to relevant moments during debriefing.",
        "why": "Important details can be missed when a simulation is reviewed only from memory. A prepared recording and marking workflow gives instructors a concrete basis for discussing participant actions and decisions.",
        "who": [
          "Simulation education centres",
          "Instructors and training programme owners",
          "Teams designing an AV environment for scenario-based learning"
        ],
        "where": "Simulation and teaching spaces with an agreed camera, audio, network and recording design.",
        "when": "When a practical scenario needs to be recorded and reviewed in a structured teaching workflow.",
        "how": [
          "Agree what instructors need to observe and review.",
          "Plan viewpoints, sound, controls and recording responsibilities.",
          "Verify capture and markers against the actual room and workflow.",
          "Agree how recordings are reviewed, stored and managed."
        ],
        "differentiators": [
          "Teaching workflow and AV design are considered together.",
          "Camera, sound, recording and software integration can be coordinated by the same team."
        ],
        "benefits": [
          "Concrete material for a debriefing conversation",
          "A connection between the scenario and its technical capture",
          "An organised way to return to important moments"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Scenario workflow",
            "description": "Prepare the AV setup around the teaching scenario and instructor needs.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Cameras and sound",
            "description": "Capture the agreed viewpoints and audio sources.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Recording and markers",
            "description": "Preserve the session and mark important moments for later review.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Debriefing support",
            "description": "Use the captured material as a basis for discussion after the simulation.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Simulation instructors",
            "need": "Discuss a decision using the actual session",
            "solution": "Mark the relevant moment and return to the captured material during debriefing.",
            "expectedBenefit": "A more concrete review conversation."
          },
          {
            "audience": "Education centres",
            "need": "Coordinate several observation sources",
            "solution": "Design the room’s capture and review workflow around its scenarios.",
            "expectedBenefit": "A more usable technical teaching environment."
          }
        ],
        "limitations": [
          "Multi-track recording does not establish universally synchronised playback of every source.",
          "Camera count, timing behaviour, controls and compatibility require installation-specific checks.",
          "Recording consent, access, storage and retention rules must be agreed by the organisation."
        ],
        "tags": [
          "SIMROOM",
          "simulation-training",
          "live-video",
          "hardware",
          "custom-software"
        ],
        "relatedProjectIds": [
          "hardware",
          "software",
          "stream",
          "forge"
        ],
        "details": {
          "aliases": [
            "SIMROOM",
            "SIMROOM: AV systems for simulation training and debriefing"
          ],
          "domainIds": [
            "simulation-training",
            "live-video",
            "hardware",
            "custom-software"
          ],
          "positioning": {
            "category": "SIMROOM: AV systems for simulation training and debriefing",
            "elevatorPitch": "An AV workflow for simulation training that connects scenarios, cameras, audio, recording, important-moment markers and subsequent debriefing.",
            "marketRole": "SIMROOM supports the path from a training scenario to a review of what happened. Cameras, sound and recording are connected with event markers so instructors can return to relevant moments during debriefing.",
            "offeringBoundaries": [
              "Multi-track recording does not establish universally synchronised playback of every source.",
              "Camera count, timing behaviour, controls and compatibility require installation-specific checks.",
              "Recording consent, access, storage and retention rules must be agreed by the organisation."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "SIMROOM supports the path from a training scenario to a review of what happened. Cameras, sound and recording are connected with event markers so instructors can return to relevant moments during debriefing.",
            "notEstablished": [
              "Multi-track recording does not establish universally synchronised playback of every source.",
              "Camera count, timing behaviour, controls and compatibility require installation-specific checks.",
              "Recording consent, access, storage and retention rules must be agreed by the organisation."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "SIMROOM supports the path from a training scenario to a review of what happened. Cameras, sound and recording are connected with event markers so instructors can return to relevant moments during debriefing."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Simulation education centres",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Simulation education centres"
              ],
              "pains": [
                "Important details can be missed when a simulation is reviewed only from memory. A prepared recording and marking workflow gives instructors a concrete basis for discussing participant actions and decisions."
              ],
              "triggers": [
                "When a practical scenario needs to be recorded and reviewed in a structured teaching workflow."
              ],
              "fitConditions": [
                "Training scenarios, room conditions and instructor requirements",
                "Agreed participant permissions, retention rules and authorised access"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Instructors and training programme owners",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Instructors and training programme owners"
              ],
              "pains": [
                "Important details can be missed when a simulation is reviewed only from memory. A prepared recording and marking workflow gives instructors a concrete basis for discussing participant actions and decisions."
              ],
              "triggers": [
                "When a practical scenario needs to be recorded and reviewed in a structured teaching workflow."
              ],
              "fitConditions": [
                "Training scenarios, room conditions and instructor requirements",
                "Agreed participant permissions, retention rules and authorised access"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Teams designing an AV environment for scenario-based learning",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Teams designing an AV environment for scenario-based learning"
              ],
              "pains": [
                "Important details can be missed when a simulation is reviewed only from memory. A prepared recording and marking workflow gives instructors a concrete basis for discussing participant actions and decisions."
              ],
              "triggers": [
                "When a practical scenario needs to be recorded and reviewed in a structured teaching workflow."
              ],
              "fitConditions": [
                "Training scenarios, room conditions and instructor requirements",
                "Agreed participant permissions, retention rules and authorised access"
              ]
            }
          ],
          "systemModel": {
            "principle": "SIMROOM supports the path from a training scenario to a review of what happened. Cameras, sound and recording are connected with event markers so instructors can return to relevant moments during debriefing.",
            "components": [
              {
                "id": "component-1",
                "name": "Scenario workflow",
                "purpose": "Prepare the AV setup around the teaching scenario and instructor needs.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Cameras and sound",
                "purpose": "Capture the agreed viewpoints and audio sources.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Recording and markers",
                "purpose": "Preserve the session and mark important moments for later review.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Debriefing support",
                "purpose": "Use the captured material as a basis for discussion after the simulation.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "Training scenarios, room conditions and instructor requirements",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Agreed participant permissions, retention rules and authorised access",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "An agreed AV capture and review workflow",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Recordings and event markers within the configured scope",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Understand the teaching scenario",
                "description": "Agree what instructors need to observe and review.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree what instructors need to observe and review."
                ],
                "outputNames": [
                  "Understand the teaching scenario"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Design the AV arrangement",
                "description": "Plan viewpoints, sound, controls and recording responsibilities.",
                "customerContribution": [],
                "providerContribution": [
                  "Plan viewpoints, sound, controls and recording responsibilities."
                ],
                "outputNames": [
                  "Design the AV arrangement"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Check a representative session",
                "description": "Verify capture and markers against the actual room and workflow.",
                "customerContribution": [],
                "providerContribution": [
                  "Verify capture and markers against the actual room and workflow."
                ],
                "outputNames": [
                  "Check a representative session"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Prepare debriefing and operation",
                "description": "Agree how recordings are reviewed, stored and managed.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree how recordings are reviewed, stored and managed."
                ],
                "outputNames": [
                  "Prepare debriefing and operation"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "Training scenarios, room conditions and instructor requirements",
              "Agreed participant permissions, retention rules and authorised access"
            ],
            "customerResponsibilities": [
              "Training scenarios, room conditions and instructor requirements",
              "Agreed participant permissions, retention rules and authorised access"
            ],
            "providerResponsibilities": [
              "An agreed AV capture and review workflow",
              "Recordings and event markers within the configured scope"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Multi-track recording does not establish universally synchronised playback of every source.",
              "Camera count, timing behaviour, controls and compatibility require installation-specific checks.",
              "Recording consent, access, storage and retention rules must be agreed by the organisation."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Room AV equipment",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Check the actual camera, audio and control interfaces for the installation.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "id": "integration-2",
              "name": "Teaching workflow",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Define recording access, marker use and the debriefing process with instructors.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "Concrete material for a debriefing conversation",
              "mechanism": "Important details can be missed when a simulation is reviewed only from memory. A prepared recording and marking workflow gives instructors a concrete basis for discussing participant actions and decisions.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "A connection between the scenario and its technical capture",
              "mechanism": "Important details can be missed when a simulation is reviewed only from memory. A prepared recording and marking workflow gives instructors a concrete basis for discussing participant actions and decisions.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "An organised way to return to important moments",
              "mechanism": "Important details can be missed when a simulation is reviewed only from memory. A prepared recording and marking workflow gives instructors a concrete basis for discussing participant actions and decisions.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When a practical scenario needs to be recorded and reviewed in a structured teaching workflow."
            ],
            "poorFitSignals": [
              "Multi-track recording does not establish universally synchronised playback of every source.",
              "Camera count, timing behaviour, controls and compatibility require installation-specific checks.",
              "Recording consent, access, storage and retention rules must be agreed by the organisation."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Multi-track recording does not establish universally synchronised playback of every source.",
              "Camera count, timing behaviour, controls and compatibility require installation-specific checks.",
              "Recording consent, access, storage and retention rules must be agreed by the organisation."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Does multi-track recording guarantee all views play in perfect sync?",
              "answer": "No general guarantee is made. Timing and playback behaviour must be tested for the actual setup.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Can this be adapted to our teaching room?",
              "answer": "We start with the room, scenarios and instructors’ needs, then assess the equipment and workflow required.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/simroom-av-simulation-training/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "software",
        "name": "Software and web applications",
        "brand": "LIVE4K",
        "kind": "service",
        "availability": "by-arrangement",
        "website": "https://live4k.media/",
        "summary": "Design, development and ongoing improvement of business applications, system integrations and automation of repetitive work.",
        "what": "We develop software around the way your business works. The scope can include a web application, an API connection between existing tools, process automation and the environment needed to operate the result.",
        "why": "Manual transfers and fragmented tools create work between systems. A focused application or integration can connect the process without assuming that every existing platform needs to be replaced.",
        "who": [
          "Companies with a process that off-the-shelf tools do not cover well",
          "Teams transferring data between business systems",
          "Organisations needing to develop an existing application"
        ],
        "where": "In the agreed hosting and integration environment, with remote collaboration and on-site discovery where useful.",
        "when": "When repeated work, missing connections or application limitations are holding a business process back.",
        "how": [
          "Map users, current tools, data and the desired outcome.",
          "Agree the first deliverable, interfaces and acceptance criteria.",
          "Build in agreed steps and review working results.",
          "Check the agreed behaviour, document responsibilities and plan further development."
        ],
        "differentiators": [
          "Software development connects to our own infrastructure and hardware work.",
          "Integration requirements can be assessed alongside the underlying process."
        ],
        "benefits": [
          "Less disconnected handling between tools",
          "A clearer fit between software and the process",
          "Development that considers the subsequent operating environment"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Business applications",
            "description": "Design and develop an application around agreed users, data and workflows.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "API integrations",
            "description": "Connect supported interfaces with explicit data and error-handling rules.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "Automation",
            "description": "Turn a defined repetitive process into a controlled software workflow.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Ongoing development",
            "description": "Improve an existing solution in agreed iterations and prepare its operating needs.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Operations teams",
            "need": "Stop re-entering the same data",
            "solution": "Connect the relevant supported interfaces with clear ownership and error handling.",
            "expectedBenefit": "Less repetitive transfer work."
          },
          {
            "audience": "Business teams",
            "need": "Support a process that standard software misses",
            "solution": "Build a focused application with agreed users and acceptance criteria.",
            "expectedBenefit": "A tool designed around the actual workflow."
          }
        ],
        "limitations": [
          "Features, source delivery, hosting, support and service levels are contractual scope decisions.",
          "Integration depends on the actual APIs, permissions and data quality.",
          "A public portfolio description is not a fixed-price package or delivery guarantee."
        ],
        "tags": [
          "Software and web applications",
          "custom-software",
          "customer-relationships",
          "infrastructure"
        ],
        "relatedProjectIds": [
          "hardware",
          "infrastructure",
          "agents",
          "stream"
        ],
        "details": {
          "aliases": [
            "Software and web applications",
            "Custom software and web application development"
          ],
          "domainIds": [
            "custom-software",
            "customer-relationships",
            "infrastructure"
          ],
          "positioning": {
            "category": "Custom software and web application development",
            "elevatorPitch": "Design, development and ongoing improvement of business applications, system integrations and automation of repetitive work.",
            "marketRole": "We develop software around the way your business works. The scope can include a web application, an API connection between existing tools, process automation and the environment needed to operate the result.",
            "offeringBoundaries": [
              "Features, source delivery, hosting, support and service levels are contractual scope decisions.",
              "Integration depends on the actual APIs, permissions and data quality.",
              "A public portfolio description is not a fixed-price package or delivery guarantee."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "We develop software around the way your business works. The scope can include a web application, an API connection between existing tools, process automation and the environment needed to operate the result.",
            "notEstablished": [
              "Features, source delivery, hosting, support and service levels are contractual scope decisions.",
              "Integration depends on the actual APIs, permissions and data quality.",
              "A public portfolio description is not a fixed-price package or delivery guarantee."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "We develop software around the way your business works. The scope can include a web application, an API connection between existing tools, process automation and the environment needed to operate the result."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Companies with a process that off-the-shelf tools do not cover well",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Companies with a process that off-the-shelf tools do not cover well"
              ],
              "pains": [
                "Manual transfers and fragmented tools create work between systems. A focused application or integration can connect the process without assuming that every existing platform needs to be replaced."
              ],
              "triggers": [
                "When repeated work, missing connections or application limitations are holding a business process back."
              ],
              "fitConditions": [
                "A business owner, intended users and a concrete process",
                "Authorised access to relevant interfaces and test data"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Teams transferring data between business systems",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Teams transferring data between business systems"
              ],
              "pains": [
                "Manual transfers and fragmented tools create work between systems. A focused application or integration can connect the process without assuming that every existing platform needs to be replaced."
              ],
              "triggers": [
                "When repeated work, missing connections or application limitations are holding a business process back."
              ],
              "fitConditions": [
                "A business owner, intended users and a concrete process",
                "Authorised access to relevant interfaces and test data"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Organisations needing to develop an existing application",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Organisations needing to develop an existing application"
              ],
              "pains": [
                "Manual transfers and fragmented tools create work between systems. A focused application or integration can connect the process without assuming that every existing platform needs to be replaced."
              ],
              "triggers": [
                "When repeated work, missing connections or application limitations are holding a business process back."
              ],
              "fitConditions": [
                "A business owner, intended users and a concrete process",
                "Authorised access to relevant interfaces and test data"
              ]
            }
          ],
          "systemModel": {
            "principle": "We develop software around the way your business works. The scope can include a web application, an API connection between existing tools, process automation and the environment needed to operate the result.",
            "components": [
              {
                "id": "component-1",
                "name": "Business applications",
                "purpose": "Design and develop an application around agreed users, data and workflows.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "API integrations",
                "purpose": "Connect supported interfaces with explicit data and error-handling rules.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "Automation",
                "purpose": "Turn a defined repetitive process into a controlled software workflow.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Ongoing development",
                "purpose": "Improve an existing solution in agreed iterations and prepare its operating needs.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "A business owner, intended users and a concrete process",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Authorised access to relevant interfaces and test data",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "The agreed application, integration or automation",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Handover materials and operating arrangements within the contract",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Understand the process",
                "description": "Map users, current tools, data and the desired outcome.",
                "customerContribution": [],
                "providerContribution": [
                  "Map users, current tools, data and the desired outcome."
                ],
                "outputNames": [
                  "Understand the process"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Define a useful scope",
                "description": "Agree the first deliverable, interfaces and acceptance criteria.",
                "customerContribution": [],
                "providerContribution": [
                  "Agree the first deliverable, interfaces and acceptance criteria."
                ],
                "outputNames": [
                  "Define a useful scope"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Develop and review",
                "description": "Build in agreed steps and review working results.",
                "customerContribution": [],
                "providerContribution": [
                  "Build in agreed steps and review working results."
                ],
                "outputNames": [
                  "Develop and review"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Hand over and operate",
                "description": "Check the agreed behaviour, document responsibilities and plan further development.",
                "customerContribution": [],
                "providerContribution": [
                  "Check the agreed behaviour, document responsibilities and plan further development."
                ],
                "outputNames": [
                  "Hand over and operate"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "A business owner, intended users and a concrete process",
              "Authorised access to relevant interfaces and test data"
            ],
            "customerResponsibilities": [
              "A business owner, intended users and a concrete process",
              "Authorised access to relevant interfaces and test data"
            ],
            "providerResponsibilities": [
              "The agreed application, integration or automation",
              "Handover materials and operating arrangements within the contract"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Features, source delivery, hosting, support and service levels are contractual scope decisions.",
              "Integration depends on the actual APIs, permissions and data quality.",
              "A public portfolio description is not a fixed-price package or delivery guarantee."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Business systems and APIs",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Assess documentation, authentication, data mapping, limits and failure behaviour for each connection.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "id": "integration-2",
              "name": "Infrastructure",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Prepare an appropriate operating environment where hosting and management form part of the project.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "Less disconnected handling between tools",
              "mechanism": "Manual transfers and fragmented tools create work between systems. A focused application or integration can connect the process without assuming that every existing platform needs to be replaced.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "A clearer fit between software and the process",
              "mechanism": "Manual transfers and fragmented tools create work between systems. A focused application or integration can connect the process without assuming that every existing platform needs to be replaced.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Development that considers the subsequent operating environment",
              "mechanism": "Manual transfers and fragmented tools create work between systems. A focused application or integration can connect the process without assuming that every existing platform needs to be replaced.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When repeated work, missing connections or application limitations are holding a business process back."
            ],
            "poorFitSignals": [
              "Features, source delivery, hosting, support and service levels are contractual scope decisions.",
              "Integration depends on the actual APIs, permissions and data quality.",
              "A public portfolio description is not a fixed-price package or delivery guarantee."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Features, source delivery, hosting, support and service levels are contractual scope decisions.",
              "Integration depends on the actual APIs, permissions and data quality.",
              "A public portfolio description is not a fixed-price package or delivery guarantee."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Can you connect our existing systems?",
              "answer": "We assess the available interfaces, documentation and permissions before confirming the scope.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Can you also operate the application?",
              "answer": "Hosting and management can be considered with the development project. Responsibilities and service terms must be agreed explicitly.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/custom-software-web-development/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "stage",
        "name": "STAGE turnkey event service",
        "brand": "LIVE4K",
        "kind": "service",
        "availability": "by-arrangement",
        "website": "https://live4k.media/projects/stage-event-interpretation-turnkey/",
        "summary": "A turnkey event service from LIVE4K using STAGE software by BizWants. We provide setup, the required equipment, audio connections, rehearsal and on-site operation for interpretation, AI translation and live captions.",
        "what": "LIVE4K delivers the complete event service: we plan the setup, provide the agreed equipment, connect the audio, configure listening and captions, rehearse and operate the service during the programme. The underlying STAGE software is provided by BizWants; it is not LIVE4K software.",
        "why": "Language and listening conditions can prevent people from following a programme. A browser-based audience entry point reduces the need to distribute dedicated receivers for the supported scenarios.",
        "who": [
          "Conference and multilingual event organisers",
          "Venues and corporate event teams",
          "Production partners planning language access"
        ],
        "where": "At events with suitable source audio and audience connectivity. Participants use their own compatible mobile devices and headphones.",
        "when": "When your programme needs live text, translated content or access to an interpretation audio channel.",
        "how": [
          "Confirm source languages, required outputs and the audience experience.",
          "Connect a suitable source signal and check the venue network.",
          "Check QR access, device playback and any captions.",
          "Monitor the agreed setup and manage the handover between production and the platform."
        ],
        "differentiators": [
          "BizWants provides the STAGE software. LIVE4K provides the complete event service, including equipment and operators.",
          "Audience access can use a QR link instead of a separate receiver handout."
        ],
        "benefits": [
          "A practical entry point on audience members’ own devices",
          "Language access considered within the technical event plan",
          "Text and audio options suited to the agreed programme"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Turnkey delivery by LIVE4K",
            "description": "Planning, required equipment, audio connections, configuration, rehearsal and on-site operation within the agreed scope.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Live transcription",
            "description": "Turn the supported source speech into live text.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "AI translation",
            "description": "Provide supported translated output after confirming languages and the selected mode.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Mobile listening",
            "description": "Let participants access the relevant audio through a QR link and their own device.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-5",
            "name": "Captions for displays",
            "description": "Prepare the supported caption output for projection or streaming as agreed.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Conference organisers",
            "need": "Help participants follow a multilingual programme",
            "solution": "Plan supported translation and audience mobile access alongside the AV setup.",
            "expectedBenefit": "Broader access to the programme."
          },
          {
            "audience": "Production teams",
            "need": "Provide live captions",
            "solution": "Prepare the supported caption output for an agreed display or stream.",
            "expectedBenefit": "An additional way to follow spoken content."
          }
        ],
        "limitations": [
          "STAGE software is supplied by BizWants. LIVE4K offers a turnkey event service with equipment and operators, rather than its own software product.",
          "The showreel mentions 33 languages; current language directions, voices and modes must be checked before an offer.",
          "AI output quality depends on source audio, speech and language; it is not a guarantee of error-free interpretation.",
          "Connectivity, participant equipment, licensing and the chosen operating mode need agreement."
        ],
        "tags": [
          "STAGE turnkey event service",
          "language-access",
          "event-production",
          "live-video"
        ],
        "relatedProjectIds": [
          "events",
          "stream"
        ],
        "details": {
          "aliases": [
            "STAGE turnkey event service",
            "STAGE: turnkey event interpretation, translation and captions"
          ],
          "domainIds": [
            "language-access",
            "event-production",
            "live-video"
          ],
          "positioning": {
            "category": "STAGE: turnkey event interpretation, translation and captions",
            "elevatorPitch": "A turnkey event service from LIVE4K using STAGE software by BizWants. We provide setup, the required equipment, audio connections, rehearsal and on-site operation for interpretation, AI translation and live captions.",
            "marketRole": "LIVE4K delivers the complete event service: we plan the setup, provide the agreed equipment, connect the audio, configure listening and captions, rehearse and operate the service during the programme. The underlying STAGE software is provided by BizWants; it is not LIVE4K software.",
            "offeringBoundaries": [
              "STAGE software is supplied by BizWants. LIVE4K offers a turnkey event service with equipment and operators, rather than its own software product.",
              "The showreel mentions 33 languages; current language directions, voices and modes must be checked before an offer.",
              "AI output quality depends on source audio, speech and language; it is not a guarantee of error-free interpretation.",
              "Connectivity, participant equipment, licensing and the chosen operating mode need agreement."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "LIVE4K delivers the complete event service: we plan the setup, provide the agreed equipment, connect the audio, configure listening and captions, rehearse and operate the service during the programme. The underlying STAGE software is provided by BizWants; it is not LIVE4K software.",
            "notEstablished": [
              "STAGE software is supplied by BizWants. LIVE4K offers a turnkey event service with equipment and operators, rather than its own software product.",
              "The showreel mentions 33 languages; current language directions, voices and modes must be checked before an offer.",
              "AI output quality depends on source audio, speech and language; it is not a guarantee of error-free interpretation.",
              "Connectivity, participant equipment, licensing and the chosen operating mode need agreement."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Turnkey event service provider",
              "scope": "Deployment planning, the required equipment, audio connections, configuration, rehearsal and on-site operation."
            },
            {
              "organization": "BizWants",
              "role": "STAGE software provider",
              "scope": "The underlying software platform; STAGE is not LIVE4K software."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Conference and multilingual event organisers",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Conference and multilingual event organisers"
              ],
              "pains": [
                "Language and listening conditions can prevent people from following a programme. A browser-based audience entry point reduces the need to distribute dedicated receivers for the supported scenarios."
              ],
              "triggers": [
                "When your programme needs live text, translated content or access to an interpretation audio channel."
              ],
              "fitConditions": [
                "Programme, audience language needs and coordination with the venue",
                "Access for setup and rehearsal, agreed venue connectivity and compatible audience devices"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Venues and corporate event teams",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Venues and corporate event teams"
              ],
              "pains": [
                "Language and listening conditions can prevent people from following a programme. A browser-based audience entry point reduces the need to distribute dedicated receivers for the supported scenarios."
              ],
              "triggers": [
                "When your programme needs live text, translated content or access to an interpretation audio channel."
              ],
              "fitConditions": [
                "Programme, audience language needs and coordination with the venue",
                "Access for setup and rehearsal, agreed venue connectivity and compatible audience devices"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Production partners planning language access",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Production partners planning language access"
              ],
              "pains": [
                "Language and listening conditions can prevent people from following a programme. A browser-based audience entry point reduces the need to distribute dedicated receivers for the supported scenarios."
              ],
              "triggers": [
                "When your programme needs live text, translated content or access to an interpretation audio channel."
              ],
              "fitConditions": [
                "Programme, audience language needs and coordination with the venue",
                "Access for setup and rehearsal, agreed venue connectivity and compatible audience devices"
              ]
            }
          ],
          "systemModel": {
            "principle": "LIVE4K delivers the complete event service: we plan the setup, provide the agreed equipment, connect the audio, configure listening and captions, rehearse and operate the service during the programme. The underlying STAGE software is provided by BizWants; it is not LIVE4K software.",
            "components": [
              {
                "id": "component-1",
                "name": "Turnkey delivery by LIVE4K",
                "purpose": "Planning, required equipment, audio connections, configuration, rehearsal and on-site operation within the agreed scope.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Live transcription",
                "purpose": "Turn the supported source speech into live text.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "AI translation",
                "purpose": "Provide supported translated output after confirming languages and the selected mode.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Mobile listening",
                "purpose": "Let participants access the relevant audio through a QR link and their own device.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-5",
                "name": "Captions for displays",
                "purpose": "Prepare the supported caption output for projection or streaming as agreed.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "Programme, audience language needs and coordination with the venue",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Access for setup and rehearsal, agreed venue connectivity and compatible audience devices",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "A configured and operated event service with the agreed equipment and LIVE4K crew",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Agreed live text, translated or listening channels, audience access links and supported display output",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Define language needs",
                "description": "Confirm source languages, required outputs and the audience experience.",
                "customerContribution": [],
                "providerContribution": [
                  "Confirm source languages, required outputs and the audience experience."
                ],
                "outputNames": [
                  "Define language needs"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Prepare the audio path",
                "description": "Connect a suitable source signal and check the venue network.",
                "customerContribution": [],
                "providerContribution": [
                  "Connect a suitable source signal and check the venue network."
                ],
                "outputNames": [
                  "Prepare the audio path"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Test the audience journey",
                "description": "Check QR access, device playback and any captions.",
                "customerContribution": [],
                "providerContribution": [
                  "Check QR access, device playback and any captions."
                ],
                "outputNames": [
                  "Test the audience journey"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Operate the event",
                "description": "Monitor the agreed setup and manage the handover between production and the platform.",
                "customerContribution": [],
                "providerContribution": [
                  "Monitor the agreed setup and manage the handover between production and the platform."
                ],
                "outputNames": [
                  "Operate the event"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "Programme, audience language needs and coordination with the venue",
              "Access for setup and rehearsal, agreed venue connectivity and compatible audience devices"
            ],
            "customerResponsibilities": [
              "Programme, audience language needs and coordination with the venue",
              "Access for setup and rehearsal, agreed venue connectivity and compatible audience devices"
            ],
            "providerResponsibilities": [
              "A configured and operated event service with the agreed equipment and LIVE4K crew",
              "Agreed live text, translated or listening channels, audience access links and supported display output"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "STAGE software is supplied by BizWants. LIVE4K offers a turnkey event service with equipment and operators, rather than its own software product.",
              "The showreel mentions 33 languages; current language directions, voices and modes must be checked before an offer.",
              "AI output quality depends on source audio, speech and language; it is not a guarantee of error-free interpretation.",
              "Connectivity, participant equipment, licensing and the chosen operating mode need agreement."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Event audio",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Connect the agreed audio source and verify levels, routing and the required channel.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "id": "integration-2",
              "name": "Projection and live streaming",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Check the caption format, display environment and production workflow before the event.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "A practical entry point on audience members’ own devices",
              "mechanism": "Language and listening conditions can prevent people from following a programme. A browser-based audience entry point reduces the need to distribute dedicated receivers for the supported scenarios.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Language access considered within the technical event plan",
              "mechanism": "Language and listening conditions can prevent people from following a programme. A browser-based audience entry point reduces the need to distribute dedicated receivers for the supported scenarios.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Text and audio options suited to the agreed programme",
              "mechanism": "Language and listening conditions can prevent people from following a programme. A browser-based audience entry point reduces the need to distribute dedicated receivers for the supported scenarios.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When your programme needs live text, translated content or access to an interpretation audio channel."
            ],
            "poorFitSignals": [
              "STAGE software is supplied by BizWants. LIVE4K offers a turnkey event service with equipment and operators, rather than its own software product.",
              "The showreel mentions 33 languages; current language directions, voices and modes must be checked before an offer.",
              "AI output quality depends on source audio, speech and language; it is not a guarantee of error-free interpretation.",
              "Connectivity, participant equipment, licensing and the chosen operating mode need agreement."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "STAGE software is supplied by BizWants. LIVE4K offers a turnkey event service with equipment and operators, rather than its own software product.",
              "The showreel mentions 33 languages; current language directions, voices and modes must be checked before an offer.",
              "AI output quality depends on source audio, speech and language; it is not a guarantee of error-free interpretation.",
              "Connectivity, participant equipment, licensing and the chosen operating mode need agreement."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Who supplies the software and who runs the event service?",
              "answer": "BizWants supplies STAGE software. LIVE4K delivers the service on a turnkey basis, including the agreed equipment, setup, audio connections, rehearsal and operators.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Are all language combinations available?",
              "answer": "Do not assume that. The presentation mentions 33 languages, but the required directions, voices and mode must be confirmed for the event.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/stage-event-interpretation-turnkey/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "stream",
        "name": "LIVE4K STREAM",
        "brand": "LIVE4K",
        "kind": "product",
        "availability": "by-arrangement",
        "website": "https://stream.live4k.media/",
        "summary": "Manage live video from inputs and compositions to output qualities, distribution, HLS playback and recording, with an API for integrations.",
        "what": "LIVE4K STREAM connects video sources, processing and outputs in a controlled streaming workflow. It supports preparing compositions and output variants and connecting them to playback, distribution and recording as required.",
        "why": "Live video often crosses several systems and network boundaries. A coordinated workflow and API make it easier to treat signal routing and distribution as part of a wider production or business process.",
        "who": [
          "Event and broadcast producers",
          "Companies with internal or external live video",
          "Software teams integrating live video workflows"
        ],
        "where": "Streaming infrastructure connected to the production environment and agreed distribution destinations. Available connectivity must be checked.",
        "when": "When you need to coordinate several inputs, output variants, playback or recording rather than send one isolated feed.",
        "how": [
          "Identify sources, audiences, output qualities and destinations.",
          "Configure the agreed processing, compositions and routes.",
          "Verify sources, network paths, playback and recording under the intended conditions.",
          "Run the transmission and hand over the agreed outputs and operating responsibilities."
        ],
        "differentiators": [
          "Production experience informs the platform and its signal workflows.",
          "Our own API connects streaming control to custom software where appropriate."
        ],
        "benefits": [
          "A coordinated path from source to destination",
          "Control that can connect to another system",
          "Playback and recording planned with the live workflow"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Inputs and compositions",
            "description": "Bring sources into a workflow and prepare the required picture compositions.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Output qualities and distribution",
            "description": "Prepare agreed quality variants and route them to supported destinations.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "HLS playback and recording",
            "description": "Connect the output to HLS playback and preserve recordings within the agreed setup.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "API integration",
            "description": "Connect supported control functions to other applications and processes.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Event producers",
            "need": "Distribute one production to several destinations",
            "solution": "Plan sources, compositions and output variants together.",
            "expectedBenefit": "A clearer and more manageable distribution workflow."
          },
          {
            "audience": "Business application teams",
            "need": "Control live video from another system",
            "solution": "Connect agreed API operations to the application workflow.",
            "expectedBenefit": "Less disconnected manual coordination."
          }
        ],
        "limitations": [
          "Support for a video protocol does not imply a complete social-account publishing API.",
          "Bitrates, latency, viewer capacity and network resilience require a concrete design.",
          "Availability and access control are agreed for each deployment; no universal SLA is implied."
        ],
        "tags": [
          "LIVE4K STREAM",
          "live-video",
          "infrastructure"
        ],
        "relatedProjectIds": [
          "events",
          "stage",
          "simroom",
          "infrastructure",
          "software",
          "water-sight"
        ],
        "details": {
          "aliases": [
            "LIVE4K STREAM",
            "LIVE4K STREAM: live video streaming and distribution"
          ],
          "domainIds": [
            "live-video",
            "infrastructure"
          ],
          "positioning": {
            "category": "LIVE4K STREAM: live video streaming and distribution",
            "elevatorPitch": "Manage live video from inputs and compositions to output qualities, distribution, HLS playback and recording, with an API for integrations.",
            "marketRole": "LIVE4K STREAM connects video sources, processing and outputs in a controlled streaming workflow. It supports preparing compositions and output variants and connecting them to playback, distribution and recording as required.",
            "offeringBoundaries": [
              "Support for a video protocol does not imply a complete social-account publishing API.",
              "Bitrates, latency, viewer capacity and network resilience require a concrete design.",
              "Availability and access control are agreed for each deployment; no universal SLA is implied."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "LIVE4K STREAM connects video sources, processing and outputs in a controlled streaming workflow. It supports preparing compositions and output variants and connecting them to playback, distribution and recording as required.",
            "notEstablished": [
              "Support for a video protocol does not imply a complete social-account publishing API.",
              "Bitrates, latency, viewer capacity and network resilience require a concrete design.",
              "Availability and access control are agreed for each deployment; no universal SLA is implied."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "LIVE4K STREAM connects video sources, processing and outputs in a controlled streaming workflow. It supports preparing compositions and output variants and connecting them to playback, distribution and recording as required."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Event and broadcast producers",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Event and broadcast producers"
              ],
              "pains": [
                "Live video often crosses several systems and network boundaries. A coordinated workflow and API make it easier to treat signal routing and distribution as part of a wider production or business process."
              ],
              "triggers": [
                "When you need to coordinate several inputs, output variants, playback or recording rather than send one isolated feed."
              ],
              "fitConditions": [
                "Source formats, destinations, expected audience and access requirements",
                "Suitable connectivity and agreement on operation and support"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Companies with internal or external live video",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Companies with internal or external live video"
              ],
              "pains": [
                "Live video often crosses several systems and network boundaries. A coordinated workflow and API make it easier to treat signal routing and distribution as part of a wider production or business process."
              ],
              "triggers": [
                "When you need to coordinate several inputs, output variants, playback or recording rather than send one isolated feed."
              ],
              "fitConditions": [
                "Source formats, destinations, expected audience and access requirements",
                "Suitable connectivity and agreement on operation and support"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Software teams integrating live video workflows",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Software teams integrating live video workflows"
              ],
              "pains": [
                "Live video often crosses several systems and network boundaries. A coordinated workflow and API make it easier to treat signal routing and distribution as part of a wider production or business process."
              ],
              "triggers": [
                "When you need to coordinate several inputs, output variants, playback or recording rather than send one isolated feed."
              ],
              "fitConditions": [
                "Source formats, destinations, expected audience and access requirements",
                "Suitable connectivity and agreement on operation and support"
              ]
            }
          ],
          "systemModel": {
            "principle": "LIVE4K STREAM connects video sources, processing and outputs in a controlled streaming workflow. It supports preparing compositions and output variants and connecting them to playback, distribution and recording as required.",
            "components": [
              {
                "id": "component-1",
                "name": "Inputs and compositions",
                "purpose": "Bring sources into a workflow and prepare the required picture compositions.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Output qualities and distribution",
                "purpose": "Prepare agreed quality variants and route them to supported destinations.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "HLS playback and recording",
                "purpose": "Connect the output to HLS playback and preserve recordings within the agreed setup.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "API integration",
                "purpose": "Connect supported control functions to other applications and processes.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "Source formats, destinations, expected audience and access requirements",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Suitable connectivity and agreement on operation and support",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "Configured live video outputs and playback within scope",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Agreed recordings and integration interfaces",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Define the signal plan",
                "description": "Identify sources, audiences, output qualities and destinations.",
                "customerContribution": [],
                "providerContribution": [
                  "Identify sources, audiences, output qualities and destinations."
                ],
                "outputNames": [
                  "Define the signal plan"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Prepare the workflow",
                "description": "Configure the agreed processing, compositions and routes.",
                "customerContribution": [],
                "providerContribution": [
                  "Configure the agreed processing, compositions and routes."
                ],
                "outputNames": [
                  "Prepare the workflow"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Test end to end",
                "description": "Verify sources, network paths, playback and recording under the intended conditions.",
                "customerContribution": [],
                "providerContribution": [
                  "Verify sources, network paths, playback and recording under the intended conditions."
                ],
                "outputNames": [
                  "Test end to end"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Operate and review",
                "description": "Run the transmission and hand over the agreed outputs and operating responsibilities.",
                "customerContribution": [],
                "providerContribution": [
                  "Run the transmission and hand over the agreed outputs and operating responsibilities."
                ],
                "outputNames": [
                  "Operate and review"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "Source formats, destinations, expected audience and access requirements",
              "Suitable connectivity and agreement on operation and support"
            ],
            "customerResponsibilities": [
              "Source formats, destinations, expected audience and access requirements",
              "Suitable connectivity and agreement on operation and support"
            ],
            "providerResponsibilities": [
              "Configured live video outputs and playback within scope",
              "Agreed recordings and integration interfaces"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Support for a video protocol does not imply a complete social-account publishing API.",
              "Bitrates, latency, viewer capacity and network resilience require a concrete design.",
              "Availability and access control are agreed for each deployment; no universal SLA is implied."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Live video protocols",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Protocol compatibility is checked against the source and destination; it is separate from access to a social platform account.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "id": "integration-2",
              "name": "Custom API workflows",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Use supported endpoints to connect stream control to the agreed business or production application.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "A coordinated path from source to destination",
              "mechanism": "Live video often crosses several systems and network boundaries. A coordinated workflow and API make it easier to treat signal routing and distribution as part of a wider production or business process.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Control that can connect to another system",
              "mechanism": "Live video often crosses several systems and network boundaries. A coordinated workflow and API make it easier to treat signal routing and distribution as part of a wider production or business process.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Playback and recording planned with the live workflow",
              "mechanism": "Live video often crosses several systems and network boundaries. A coordinated workflow and API make it easier to treat signal routing and distribution as part of a wider production or business process.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When you need to coordinate several inputs, output variants, playback or recording rather than send one isolated feed."
            ],
            "poorFitSignals": [
              "Support for a video protocol does not imply a complete social-account publishing API.",
              "Bitrates, latency, viewer capacity and network resilience require a concrete design.",
              "Availability and access control are agreed for each deployment; no universal SLA is implied."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Support for a video protocol does not imply a complete social-account publishing API.",
              "Bitrates, latency, viewer capacity and network resilience require a concrete design.",
              "Availability and access control are agreed for each deployment; no universal SLA is implied."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Does protocol support mean automatic publishing to every social account?",
              "answer": "No. Transport compatibility, account permissions and platform APIs are separate matters and must be checked.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Can our software control the stream?",
              "answer": "The platform has an API. We agree the supported operations, authentication and integration scope for your system.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/live4k-stream-live-video-streaming/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    },
    {
      "revision": 2,
      "updatedAt": "2026-11-20T15:57:48.841Z",
      "project": {
        "id": "water-sight",
        "name": "Water-Sight",
        "brand": "LIVE4K",
        "kind": "product",
        "availability": "by-arrangement",
        "website": "https://water-sight.com/",
        "summary": "Monitor optical changes in water using a camera and reference target, with measurement history, images and alerts for configured thresholds.",
        "what": "Water-Sight observes water against a reference target and tracks changes in its optical appearance. A camera node and image analysis connect the physical observation to a history and an agreed alerting workflow.",
        "why": "A time series of images can reveal changes that are difficult to assess from occasional visual checks. Recording the observation and its trend provides useful context for a human operator.",
        "who": [
          "Operators who need to observe changes in water appearance",
          "Teams assessing optical monitoring at a specific installation",
          "Businesses connecting physical monitoring with data workflows"
        ],
        "where": "At a suitable water observation point whose lighting, target placement, water conditions and installation constraints have been assessed. Local operation without internet is possible in the agreed setup.",
        "when": "When changes in colour or clarity are operationally relevant and you want a documented optical trend rather than an occasional visual impression.",
        "how": [
          "Check the purpose, installation conditions and relevant changes.",
          "Prepare a stable observation arrangement and the operating environment.",
          "Configure capture, history and appropriate thresholds.",
          "Compare behaviour with the actual conditions and agree operator responsibilities."
        ],
        "differentiators": [
          "Custom hardware connects directly to the image-analysis workflow.",
          "The described design keeps the electronics above the water, with inert glass and ceramics in contact with it."
        ],
        "benefits": [
          "A recorded trend of optical appearance",
          "Images that add context to a change",
          "An additional input for an operator’s decision"
        ],
        "capabilities": [
          {
            "id": "capability-1",
            "name": "Camera and reference target",
            "description": "Observe the water against a known visual reference.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-2",
            "name": "Image analysis",
            "description": "Track defined optical changes within the configured setup.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-3",
            "name": "History and images",
            "description": "Review the development of observations over time.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          },
          {
            "id": "capability-4",
            "name": "Threshold alerts",
            "description": "Notify the agreed workflow when configured limits are crossed.",
            "status": "owner-described",
            "evidenceIds": [
              "editorial-en"
            ]
          }
        ],
        "useCases": [
          {
            "audience": "Plant operators",
            "need": "See when the appearance of water changes",
            "solution": "Track a defined observation point with images and a time history.",
            "expectedBenefit": "More context than an occasional manual look."
          },
          {
            "audience": "Technical teams",
            "need": "Assess a location for optical monitoring",
            "solution": "Run a scoped installation evaluation and compare the observations with actual conditions.",
            "expectedBenefit": "A basis for deciding whether the method fits the site."
          }
        ],
        "limitations": [
          "Optical observation is not certified chemical analysis or certified NTU measurement.",
          "Colour and clarity readings must not be presented as a universal water-quality or safety certificate.",
          "Lighting, fouling, installation and actual site conditions affect the result."
        ],
        "tags": [
          "Water-Sight",
          "water-monitoring",
          "hardware",
          "custom-software",
          "live-video"
        ],
        "relatedProjectIds": [
          "hardware",
          "software",
          "infrastructure",
          "stream"
        ],
        "details": {
          "aliases": [
            "Water-Sight",
            "Water-Sight: optical monitoring of water colour and clarity"
          ],
          "domainIds": [
            "water-monitoring",
            "hardware",
            "custom-software",
            "live-video"
          ],
          "positioning": {
            "category": "Water-Sight: optical monitoring of water colour and clarity",
            "elevatorPitch": "Monitor optical changes in water using a camera and reference target, with measurement history, images and alerts for configured thresholds.",
            "marketRole": "Water-Sight observes water against a reference target and tracks changes in its optical appearance. A camera node and image analysis connect the physical observation to a history and an agreed alerting workflow.",
            "offeringBoundaries": [
              "Optical observation is not certified chemical analysis or certified NTU measurement.",
              "Colour and clarity readings must not be presented as a universal water-quality or safety certificate.",
              "Lighting, fouling, installation and actual site conditions affect the result."
            ]
          },
          "readiness": {
            "commercialStatus": "by-arrangement",
            "documentedState": "Water-Sight observes water against a reference target and tracks changes in its optical appearance. A camera node and image analysis connect the physical observation to a history and an agreed alerting workflow.",
            "notEstablished": [
              "Optical observation is not certified chemical analysis or certified NTU measurement.",
              "Colour and clarity readings must not be presented as a universal water-quality or safety certificate.",
              "Lighting, fouling, installation and actual site conditions affect the result."
            ],
            "reviewedOn": "2026-11-20"
          },
          "providerRoles": [
            {
              "organization": "LIVE4K",
              "role": "Design and implementation within the agreed scope.",
              "scope": "Water-Sight observes water against a reference target and tracks changes in its optical appearance. A camera node and image analysis connect the physical observation to a history and an agreed alerting workflow."
            }
          ],
          "audienceProfiles": [
            {
              "id": "audience-1",
              "segment": "Operators who need to observe changes in water appearance",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Operators who need to observe changes in water appearance"
              ],
              "pains": [
                "A time series of images can reveal changes that are difficult to assess from occasional visual checks. Recording the observation and its trend provides useful context for a human operator."
              ],
              "triggers": [
                "When changes in colour or clarity are operationally relevant and you want a documented optical trend rather than an occasional visual impression."
              ],
              "fitConditions": [
                "An appropriate observation point and description of relevant changes",
                "Access, suitable installation conditions and a person responsible for interpreting alerts"
              ]
            },
            {
              "id": "audience-2",
              "segment": "Teams assessing optical monitoring at a specific installation",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Teams assessing optical monitoring at a specific installation"
              ],
              "pains": [
                "A time series of images can reveal changes that are difficult to assess from occasional visual checks. Recording the observation and its trend provides useful context for a human operator."
              ],
              "triggers": [
                "When changes in colour or clarity are operationally relevant and you want a documented optical trend rather than an occasional visual impression."
              ],
              "fitConditions": [
                "An appropriate observation point and description of relevant changes",
                "Access, suitable installation conditions and a person responsible for interpreting alerts"
              ]
            },
            {
              "id": "audience-3",
              "segment": "Businesses connecting physical monitoring with data workflows",
              "decisionRoles": [
                "The responsible business or technical owner"
              ],
              "endUsers": [
                "Businesses connecting physical monitoring with data workflows"
              ],
              "pains": [
                "A time series of images can reveal changes that are difficult to assess from occasional visual checks. Recording the observation and its trend provides useful context for a human operator."
              ],
              "triggers": [
                "When changes in colour or clarity are operationally relevant and you want a documented optical trend rather than an occasional visual impression."
              ],
              "fitConditions": [
                "An appropriate observation point and description of relevant changes",
                "Access, suitable installation conditions and a person responsible for interpreting alerts"
              ]
            }
          ],
          "systemModel": {
            "principle": "Water-Sight observes water against a reference target and tracks changes in its optical appearance. A camera node and image analysis connect the physical observation to a history and an agreed alerting workflow.",
            "components": [
              {
                "id": "component-1",
                "name": "Camera and reference target",
                "purpose": "Observe the water against a known visual reference.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-2",
                "name": "Image analysis",
                "purpose": "Track defined optical changes within the configured setup.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-3",
                "name": "History and images",
                "purpose": "Review the development of observations over time.",
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "component-4",
                "name": "Threshold alerts",
                "purpose": "Notify the agreed workflow when configured limits are crossed.",
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ],
            "inputs": [
              {
                "id": "input-1",
                "name": "Project brief",
                "description": "An appropriate observation point and description of relevant changes",
                "required": true
              },
              {
                "id": "input-2",
                "name": "Requirements and responsibilities",
                "description": "Access, suitable installation conditions and a person responsible for interpreting alerts",
                "required": true
              }
            ],
            "outputs": [
              {
                "id": "output-1",
                "name": "Agreed outcome",
                "description": "Optical observations, images and history in the agreed setup",
                "format": "As specified in the project agreement."
              },
              {
                "id": "output-2",
                "name": "Handover",
                "description": "Configured alerts and operating guidance within scope",
                "format": "As specified in the project agreement."
              }
            ],
            "workflow": [
              {
                "id": "step-1",
                "name": "Assess the observation point",
                "description": "Check the purpose, installation conditions and relevant changes.",
                "customerContribution": [],
                "providerContribution": [
                  "Check the purpose, installation conditions and relevant changes."
                ],
                "outputNames": [
                  "Assess the observation point"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-2",
                "name": "Set up the reference and camera",
                "description": "Prepare a stable observation arrangement and the operating environment.",
                "customerContribution": [],
                "providerContribution": [
                  "Prepare a stable observation arrangement and the operating environment."
                ],
                "outputNames": [
                  "Set up the reference and camera"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-3",
                "name": "Establish the observation workflow",
                "description": "Configure capture, history and appropriate thresholds.",
                "customerContribution": [],
                "providerContribution": [
                  "Configure capture, history and appropriate thresholds."
                ],
                "outputNames": [
                  "Establish the observation workflow"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              },
              {
                "id": "step-4",
                "name": "Validate in place",
                "description": "Compare behaviour with the actual conditions and agree operator responsibilities.",
                "customerContribution": [],
                "providerContribution": [
                  "Compare behaviour with the actual conditions and agree operator responsibilities."
                ],
                "outputNames": [
                  "Validate in place"
                ],
                "evidenceIds": [
                  "editorial-en"
                ]
              }
            ]
          },
          "delivery": {
            "engagementModels": [
              "Project scope agreed individually."
            ],
            "operationModes": [
              "Operating model and responsibilities agreed for the actual use case."
            ],
            "prerequisites": [
              "An appropriate observation point and description of relevant changes",
              "Access, suitable installation conditions and a person responsible for interpreting alerts"
            ],
            "customerResponsibilities": [
              "An appropriate observation point and description of relevant changes",
              "Access, suitable installation conditions and a person responsible for interpreting alerts"
            ],
            "providerResponsibilities": [
              "Optical observations, images and history in the agreed setup",
              "Configured alerts and operating guidance within scope"
            ],
            "acceptanceChecks": [
              "Review the agreed functions and deliverables against the project brief.",
              "Confirm relevant interfaces, responsibilities and limitations."
            ],
            "scopeDrivers": [
              "Optical observation is not certified chemical analysis or certified NTU measurement.",
              "Colour and clarity readings must not be presented as a universal water-quality or safety certificate.",
              "Lighting, fouling, installation and actual site conditions affect the result."
            ]
          },
          "integrations": [
            {
              "id": "integration-1",
              "name": "Monitoring and alerting workflow",
              "category": "workflow",
              "direction": "bidirectional",
              "status": "proposed",
              "description": "Agree the available interface, destination and response process for the installation.",
              "conditions": [
                "Confirm the actual interface, permissions and scope before implementation."
              ],
              "notIncluded": [
                "Compatibility with every third-party system is not implied."
              ],
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "valueModel": [
            {
              "outcome": "A recorded trend of optical appearance",
              "mechanism": "A time series of images can reveal changes that are difficult to assess from occasional visual checks. Recording the observation and its trend provides useful context for a human operator.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "Images that add context to a change",
              "mechanism": "A time series of images can reveal changes that are difficult to assess from occasional visual checks. Recording the observation and its trend provides useful context for a human operator.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            },
            {
              "outcome": "An additional input for an operator’s decision",
              "mechanism": "A time series of images can reveal changes that are difficult to assess from occasional visual checks. Recording the observation and its trend provides useful context for a human operator.",
              "indicators": [
                "Criteria agreed for the specific project."
              ],
              "measurementNote": "An expected benefit, not a measured result or a guarantee."
            }
          ],
          "commercial": {
            "goodFitSignals": [
              "When changes in colour or clarity are operationally relevant and you want a documented optical trend rather than an occasional visual impression."
            ],
            "poorFitSignals": [
              "Optical observation is not certified chemical analysis or certified NTU measurement.",
              "Colour and clarity readings must not be presented as a universal water-quality or safety certificate.",
              "Lighting, fouling, installation and actual site conditions affect the result."
            ],
            "discoveryQuestions": [
              "What outcome should the project support?",
              "What environment and constraints apply?",
              "Who will review the result and manage its use?"
            ],
            "firstStep": "Start with a short conversation about your intended outcome, the existing environment and a useful first scope.",
            "notIncluded": [
              "Optical observation is not certified chemical analysis or certified NTU measurement.",
              "Colour and clarity readings must not be presented as a universal water-quality or safety certificate.",
              "Lighting, fouling, installation and actual site conditions affect the result."
            ]
          },
          "relationships": [],
          "faq": [
            {
              "question": "Does Water-Sight certify that water is safe?",
              "answer": "No. It observes optical changes and does not replace certified chemical testing or a safety assessment.",
              "evidenceIds": [
                "editorial-en"
              ]
            },
            {
              "question": "Does it measure certified turbidity in NTU?",
              "answer": "That is not established. The described method is optical observation with a reference target and site-specific interpretation.",
              "evidenceIds": [
                "editorial-en"
              ]
            }
          ],
          "evidence": [
            {
              "id": "editorial-en",
              "title": "English editorial adaptation of the reviewed public profile",
              "type": "editorial-analysis",
              "publicUrl": "https://live4k.media/projects/water-sight-optical-water-monitoring/",
              "reviewedOn": "2026-11-20",
              "scope": "An English adaptation of the corresponding published Czech profile and its availability boundaries.",
              "limitations": "This adaptation is not a new operational test. The Czech source profile contains the detailed source record."
            }
          ]
        }
      }
    }
  ]
}
