Bua™ Legal Notice & Intellectual Property Governance

1. Ownership & Trademark Notice

Bua™ is a registered trademark and proprietary digital platform of The Sovereign Series (Pty) Limited (“the Company”). All intellectual property rights in and to Bua™, including but not limited to software, source code, system architecture, algorithms, cryptographic mechanisms, data models, designs, trademarks, logos, content, documentation, and derivative works, are owned by or lawfully licensed to the Company, unless expressly stated otherwise.

No rights or interests are granted or implied except as explicitly authorised in writing by The Sovereign Series (Pty) Limited.

2. Restrictions on Use

Unauthorised access, use, reproduction, modification, distribution, reverse engineering, decompilation, scraping, mirroring, commercial exploitation, or circumvention of the Bua™ platform or any of its components is strictly prohibited.

Any unauthorised or improper use may result in:

• immediate suspension or termination of access,
• civil claims for damages and injunctive relief,
• regulatory notification where applicable, and
• criminal prosecution under applicable intellectual property, cybercrime, and commercial laws.

All rights are expressly reserved.

3. Enterprise, Institutional & Contractual Position

Bua™ is a proprietary technology platform. Nothing in any agreement, engagement, access grant, pilot, demonstration, or deployment shall be construed as a transfer, assignment, or implied licence of intellectual property rights, except where explicitly documented in a signed written agreement executed by authorised representatives of The Sovereign Series (Pty) Limited.

All underlying systems, enhancements, configurations, customisations, integrations, and derivative works remain the exclusive property of the Company unless otherwise agreed in writing.

4. Partnering, Co-Branding & Third-Party References

References to partners, integrators, institutions, or third parties in connection with Bua™ do not imply ownership, endorsement, joint control, or transfer of intellectual property rights.

Any use of the Bua™ name, logo, trademarks, visual identity, or platform elements by third parties requires prior written authorisation and strict adherence to the Company’s brand, governance, and usage standards.

5. Investor, Public & Regulatory Disclosure

References to Bua™ in investor materials, public communications, regulatory submissions, or informational documents are provided for descriptive purposes only and do not constitute an offer, solicitation, or commitment unless expressly stated and contractually executed.

Platform governance, data sovereignty, security controls, and intellectual property protection are enforced in accordance with applicable law and the internal governance frameworks of The Sovereign Series (Pty) Limited.

6. Enforcement & Legal Reservation

The Sovereign Series (Pty) Limited reserves the right to monitor use of the Bua™ platform and to enforce its intellectual property and contractual rights to the fullest extent permitted by law, including seeking injunctive relief, damages, and other legal remedies.

Failure to enforce any right shall not be construed as a waiver of such right.

7. Deployment & Implementation Instructions (Mandatory)

7.1 Digital Platforms (Web, Mobile, Desktop)

• Footer (short form): © The Sovereign Series (Pty) Limited. Bua™ is a registered trademark. All rights reserved.
• Full version: Accessible via “Legal”, “Terms”, or “About” sections.

7.2 Applications & APIs

• Include reference to this notice in application “About” screens, API documentation headers, and developer portals and SDK documentation.

7.3 Commercial & Legal Documents

• Append or reference this notice in proposals, contracts, enterprise onboarding packs, and licensing or access agreements.

7.4 Marketing, Media & Partner Use

• No external publication or reuse of Bua™ branding or materials is permitted without prior written approval.
• This notice supersedes all informal or verbal permissions.

8. Governing Principle

Bua™ is governed on a sovereign-first, capability-driven intellectual property model. Protection of platform integrity, brand trust, and strategic control is fundamental to its operation and evolution.

9. C# Upgrade Mandate

All modules, services, rebuilds, and refactored components must be upgraded and standardised in C#. No production functionality may remain in fragmented, obsolete, mixed-pattern, or loosely connected implementations.

This applies across the full platform stack, including backend services, business logic, integration layers, UI controllers, HTML rendering logic, background workers, installers, startup routines, health probes, telemetry pipelines, and database access components.

9.1 C# standardisation requirements

All application logic must be implemented in modern C# on the approved .NET runtime baseline.

The upgrade must ensure that:

• All core functionality is written and maintained in C#.
• All legacy or inconsistent implementations are refactored into structured C# services.
• All controllers, services, repositories, DTOs, validators, and middleware are aligned to the same C# coding standards.
• All data access is handled through C# using EF Core and SQL Server.
• All HTML rendering is driven by C# controllers, view models, partial views, and service-backed MVC patterns.
• No business logic is embedded in static HTML, scripts, or unmanaged fragments.
• All module interactions are routed through strongly typed C# interfaces and dependency injection.

9.2 Full rebuild requirement in C#

Where a module is unstable, incomplete, or structurally outdated, it must not merely be patched. It must be rebuilt properly in C# and aligned with the new architecture.

This includes:

• Rebuilding fragile modules into clean C# services.
• Replacing duplicated logic with reusable C# abstractions.
• Rewriting deprecated implementations into maintainable C# patterns.
• Converting disconnected workflows into integrated C# application flows.
• Standardising validation, error handling, logging, and security in C#.

9.3 UI and HTML alignment to C#

All web functionality must remain service-driven and C# controlled.

HTML, Razor views, and front-end rendering must be backed by:

• Strongly typed C# view models.
• C# controller actions.
• C# service orchestration.
• C# validation and security rules.
• C# session and authentication flows.

The HTML layer is presentation only. The functional engine must be C#.

9.4 Engineering rule

If a feature cannot be cleanly maintained, tested, secured, and integrated in its current form, it must be re-engineered in C#.

No module is exempt. All modules must be upgraded.

9.5 Completion criteria

The upgrade is complete only when:

• All modules are fully aligned to the unified C# architecture.
• All production logic is implemented and maintainable in C#.
• SQL Server integration is fully controlled through C# services and EF Core.
• Web, API, admin, and background services all compile and run cleanly in C#.
• Legacy non-compliant implementations are removed or replaced.
• CI passes across the full C# solution.

9.6 Ticket-ready line

Upgrade, refactor, rebuild, and standardise the entire platform in C#, ensuring that all modules are fully implemented, integrated, tested, SQL Server-aligned, and maintainable under a single modern .NET architecture.