An early product analysis and an organizational delivery process answer different questions. The first asks whether an idea deserves further work. The second asks who may decide, which evidence is needed and under what conditions the project may continue.
Forenta separates those contexts. Forge is the public analysis environment for individual users. Forenta for Business is the organizational environment, currently available through controlled pilots and guided engagements on request. Treating them as one product would create the wrong expectations about evidence, governance and readiness.
Two environments with different responsibilities
Forge starts with text. A user can submit an idea, proposition, plan or relevant written code context. The output is an AI-generated assessment of the material supplied, including assumptions, risks and a possible next step. Forge does not import a website or clone a repository from a link.
Forenta for Business starts with an organization, a project and assigned responsibilities. It adds stages, permissions, decision gates, budget limits, organization-scoped data controls and an audit record. Explicitly connected sources may provide bounded read-only context. Their contents are treated as untrusted evidence, not as instructions to the system.
Current Forenta product scope, 7 August 2026. Forenta for Business is available as a controlled pilot.
| Aspect | Forge | Forenta for Business |
|---|---|---|
| Primary user | Individual maker or founder | Organization and project team |
| Input | Text supplied by the user | Project record plus explicitly available context |
| Output | Structured analysis and next step | Stage findings, advice and a decision record |
| Authority | The user interprets the result | Authorized people decide and record overrides |
| Availability | Public beta | Controlled pilot or guided engagement |
Why an analysis is not yet governance
A clear report can still leave ownership unresolved. NIST's AI Risk Management Framework therefore describes risk management as an ongoing set of govern, map, measure and manage activities, not as a single assessment.¹ The accompanying generative AI profile adds risks and actions specific to systems that generate content or decisions from prompts and context.²
The same distinction appears in law. Article 9 of the EU AI Act requires a continuing risk-management system for high-risk AI systems.³ That requirement does not apply to every product idea, but it illustrates the broader point: where the consequences are material, risk work continues across the lifecycle.
An analysis can identify a risk. Governance determines who owns it, what evidence is sufficient and whether the project may continue while it remains open.
Eight stages with an explicit decision
The Forenta for Business process follows eight stages: idea, problem and objective; research; structured analysis; architecture; build; validation and security; deployment; monitoring and iteration. The stages make the sequence visible. They do not imply that every project needs the same amount of work.
At a decision gate, the available findings are translated into advice to proceed, revise or stop. Required items can hold the transition. Authorized people can override the advice, but the reason, the person and the original recommendation remain traceable. This keeps human authority intact without erasing the earlier warning.
Stage-gate methods have long been used to separate investment decisions in product development. Cooper's early formulation made the gates explicit, while later work warned against rigid bureaucracy and argued for more flexible processes.⁴ Boehm's spiral model approached the same problem through repeated risk analysis and prototyping.⁵ Neither method is a direct validation of Forenta, but both support the choice to make uncertainty and continuation decisions visible.
Evidence, access and budgets belong to the project
Organizational controls matter because useful context is often private. Project data is scoped to the organization and access follows roles and permissions. Connected context is read-only. Actions with material consequences remain behind explicit permissions and are written to an audit trail.
Budget oversight is part of the same control model. A project should not be able to consume unlimited model usage without an organizational boundary. The presence of a limit does not guarantee economical use, but it gives the responsible team a place to monitor and intervene.
These controls should not be read as a claim of enterprise certification or independent assurance. Forenta for Business remains a controlled offer. Deployment, operating controls and fit must be established with each organization.
The human decision remains the endpoint
RAND's 2024 interviews with 65 data scientists and engineers found that misunderstandings about the problem being solved were the most frequently reported cause of AI project failure.⁶ A stronger model does not repair a project that has no shared problem definition or accountable owner.
Forge can help expose weak assumptions early. Forenta for Business can keep those assumptions, findings and decisions connected as work progresses. Neither product decides whether an organization should accept a legal, financial, security or operational risk. That remains a human responsibility.
What is the difference between Forge and Forenta for Business?
Forge analyses text submitted by an individual user. Forenta for Business adds an organizational project process with stages, roles, permissions, decision gates, budget controls and an audit trail.
Is Forenta for Business fully self-service?
No. It is currently available through controlled pilots and guided engagements on request. The environment and operating controls must be assessed with each organization.
Does Forenta make the final project decision?
No. The system provides AI-generated findings and advice. An authorized person remains responsible for the decision and for any documented override.
References
- 1.NIST (2023). Artificial Intelligence Risk Management Framework (AI RMF 1.0).
- 2.NIST (2024). Artificial Intelligence Risk Management Framework: Generative AI Profile (NIST AI 600-1).
- 3.European Union (2024). Regulation (EU) 2024/1689, Article 9: Risk management system.
- 4.Cooper, R. G. (1990). Stage-gate systems: A new tool for managing new products. Business Horizons, 33(3), 44-54.
- 5.Boehm, B. W. (1988). A spiral model of software development and enhancement. Computer, 21(5), 61-72.
- 6.Ryseff, J., De Bruhl, B., & Newberry, S. (2024). The Root Causes of Failure for Artificial Intelligence Projects and How They Can Succeed. RAND Corporation.