Download the PHP package waysnx/business-framework without Composer

On this page you can find all versions of the php package waysnx/business-framework. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.

FAQ

After the download, you have to make one include require_once('vendor/autoload.php');. After that you have to import the classes with use statements.

Example:
If you use only one package a project is not needed. But if you use more then one package, without a project it is not possible to import the classes with use statements.

In general, it is recommended to use always a project to download your libraries. In an application normally there is more than one library needed.
Some PHP packages are not free to download and because of that hosted in private repositories. In this case some credentials are needed to access such packages. Please use the auth.json textarea to insert credentials, if a package is coming from a private repository. You can look here for more information.

  • Some hosting areas are not accessible by a terminal or SSH. Then it is not possible to use Composer.
  • To use Composer is sometimes complicated. Especially for beginners.
  • Composer needs much resources. Sometimes they are not available on a simple webspace.
  • If you are using private repositories you don't need to share your credentials. You can set up everything on our site and then you provide a simple download link to your team member.
  • Simplify your Composer build process. Use our own command line tool to download the vendor folder as binary. This makes your build process faster and you don't need to expose your credentials for private repositories.
Please rate this library. Is it a good library?

Informations about the package business-framework

WaysNX Business Framework — Laravel Implementation

Official Laravel 13 implementation of the WaysNX Business Framework (WBF).

What is WBF?

WBF is an enterprise-grade architecture framework for building business applications with structured design patterns, governance, and standardized practices. It enables teams to:

Why WBF?

Traditional applications often scatter business logic across controllers, services, and validation layers, making business intent difficult to extract and maintain. WBF inverts this approach: business structure comes first.

With WBF you define:

Then you write the implementation code. WBF provides registries, lifecycle management, and orchestration infrastructure that your application can use to register and execute its business artifacts.

What This Package Provides

This Laravel package provides:

Requirements

Installation

Install the package through Composer:

The package uses Laravel's auto-discovery. No manual service provider registration is required.

Verify Installation

After installation, verify that WBF is correctly installed and all components are available:

This command checks system health and component availability.

Core Concepts

WBF defines five core concepts that work together to structure business applications:

Module

A Module is a logical business area that groups related capabilities, entities, operations, and rules.

Entity

An Entity is a business object with identity that the application manages.

Business Function

A Business Function is a discrete business operation that performs or initiates a meaningful business action.

Validation

A Validation is a business rule or condition that determines whether data, an operation, or a situation satisfies a requirement.

Workflow

A Workflow is a defined business process that coordinates activities, decisions, states, and transitions.

How They Work Together

Concepts are organized in layers within a module:

Entities are operated on by business functions. Validation definitions provide business rules that applications can evaluate against entities and operations. Workflows orchestrate business functions and manage entity state throughout execution. Registered validation definitions can be used by applications to evaluate business rules at appropriate points.

For example, in an Employee Onboarding workflow:

Illustrative Example

Consider an audit management system (this is an illustrative example of how WBF concepts work together):

Module: AuditManagement

Entities: Audit, Finding, Evidence, Auditor, Department

Business Functions: CreateAudit, StartAudit, RecordFinding, AttachEvidence, ReviewFinding, ResolveFinding, CloseAudit

Validations: AuditMustHaveAssignedAuditor, FindingMustHaveSeverity, CriticalFindingRequiresEvidence, AuditCannotBeClosedWithUnresolvedCritical

Workflow: AuditReview

Note: This is an illustrative example showing how WBF concepts work together. It is not a claim that WaysNX Business Framework contains audit-specific functionality. Developers implement their own domain-specific modules and entities.

Quick Start

List Available Resources

Lists all available resource types. Use a specific resource type to see registered instances:

CLI Commands

The WBF Laravel package provides Artisan commands for managing, verifying, and generating business framework artifacts.

wbf:doctor — Verify System Health

Check WBF system health and component availability.

wbf:list — List Resources

List registered WBF resources (modules, entities, business functions, validations, workflows).

wbf:show — Show Resource Details

Display detailed information about a specific resource.

wbf:make — Generate Artifacts

Create new WBF artifacts with scaffolded code ready for implementation.

wbf:register — Verify Registration

Verify that a resource is registered and discoverable by the framework.

wbf:createdemo — End-to-End WBF Demonstration

Run a complete working demonstration of WBF concepts in action using a Hospital Audit Management domain.

The CREATEDemo command demonstrates:

Demo Flow

Why CREATEDemo Exists

CREATEDemo provides:

CREATEDemo is not a production business application. It is an educational demonstration designed to:

Example Output

Human-readable output:

Machine-readable output (with --json):

The following is illustrative output; execution IDs, durations, and other runtime values vary between runs.

The JSON output is suitable for automation, tooling, and AI-oriented inspection of WBF behavior.

Generated Artifacts

When you run wbf:make, the command generates scaffolded code for the specified artifact type. Output paths and namespaces are configurable via command options but default to Laravel application structure.

Generated Module

Files generated: 1 file

Factory class with static create() method returns immutable ModuleDefinition.

Generated Entity

Files generated: 1 file

Factory class with static create() method returns immutable EntityDefinition.

Generated Business Function

Files generated: 1 file

Concrete class extending WaysNX\BusinessFramework\Models\BusinessFunction with executeBusiness() method for developer implementation.

Generated Validation

Files generated: 1 file

Factory class with static create() method returns immutable ValidationDefinition.

Generated Workflow

Files generated: 2 files (atomic generation — either both created or neither)

File 1 — Technical Specification:

File 2 — Governance Model:

Both files coexist to separate technical execution concerns from business governance.

Manual Registration Required

Generated artifacts are not automatically registered to the registries. Application must manually register during bootstrap in a service provider:

Registry System

The WBF framework uses registries to discover and lookup business framework artifacts at runtime:

How Registration Works

Artifact generation (wbf:make) does NOT automatically register artifacts.

  1. Generation: wbf:make generates PHP factory classes (Definition classes) in application directories
  2. Definition: Each generated artifact has a Definition class with a static create() method that returns an immutable definition object
  3. Registration: Application code must manually register definitions during bootstrap:

  4. Discovery: Once registered, the registry provides lookup methods (findById(), findByName(), findByModule(), etc.)
  5. Execution: The WorkflowEngine uses registered workflow definitions for execution, while applications can use the ValidationRegistry to discover registered validation definitions.

Use wbf:list to view all currently registered resources in a running application.

Workflow Execution

The WorkflowEngine executes workflow definitions by coordinating business functions:

WorkflowContext

Immutable value object carrying execution context:

Workflow Execution Lifecycle

  1. Setup — WorkflowContext carries execution parameters
  2. Step Execution — Each workflow step executes in sequence
  3. Step Function Invocation — WorkflowEngine invokes business functions associated with each step
  4. Business Logic — Business functions (developer-implemented) perform domain operations
  5. State Management — Business functions handle entity state changes (not automatic)
  6. Step Completion — Engine tracks completed/failed steps
  7. Completion — WorkflowResult reports outcome and timing

WorkflowResult

Contains execution outcome:

Methods available:

Extension Points

Subclass WorkflowEngine to customize behavior:

Validation Framework

The ValidationFramework provides the structures and registration mechanisms used to define and manage validation rules. Applications are responsible for evaluating registered validation definitions.

  1. Rule Evaluation — Rules are evaluated against entities or operations
  2. Issue Reporting — Violations produce validation issues
  3. Severity Classification — Issues are classified as errors or warnings
  4. Scope Application — Validations apply to specific entity types or operation scopes
  5. Declarative Specification — Validation rules are defined separate from business logic

Current implementation: The framework provides definition and registration of validations. Validation execution remains an application responsibility. Developers can query the ValidationRegistry to retrieve registered validation definitions and implement evaluation logic appropriate to their domain.

Current Implementation Scope

The WaysNX Business Framework Laravel package focuses on:

Not currently included (planned for future phases):

This reflects Phase 1-4 implementation scope. The framework provides a solid foundation for business-first architecture. Advanced capabilities will be added as the framework evolves.

Laravel Integration

The WBF Laravel package integrates seamlessly with Laravel's service container and auto-discovery:

Using Components in Your Code

Inject WBF components into your classes via constructor injection:

Service Provider Binding

The BusinessFrameworkServiceProvider registers all WBF components:

This means:

Technology-Neutral Design

WBF is designed so its core business concepts can be implemented across different technology stacks. The fundamental concepts (Module, Entity, Business Function, Validation, Workflow) are technology-agnostic.

Currently verified implementations:

Other technology implementations may be provided as the framework evolves. The business concepts remain consistent across platforms; implementation details adapt to each platform's conventions and capabilities.

For AI Agents and Automation

WBF is designed to enable machine readability and programmatic inspection of business structure. The explicit, unambiguous concepts make it suitable for tooling and automation:

Definition vs Runtime Distinction

WBF clearly separates metadata from execution:

This separation enables:

Inspectable Metadata

Each concept provides machine-readable metadata:

Applications can query registries to discover structure:

This enables automated analysis, documentation generation, and future AI capabilities.

System Requirements

File Structure

The WBF Laravel package structure:

Documentation

For comprehensive documentation on the WaysNX Business Framework architecture, design patterns, specifications, and multi-technology implementation guidance, visit the main repository:

WaysNX Business Framework

That repository contains:

Contributing

Contributions are welcome. Please refer to the contribution guidelines in the main WaysNX Business Framework repository:

WaysNX Business Framework - Contributing

License

Apache License 2.0

See the LICENSE file for full license text.


Built with WaysNX Business Framework — Enterprise Architecture for Modern Applications


All versions of business-framework with dependencies

PHP Build Version
Package Version
Requires php Version ^8.3
illuminate/support Version ^13.0
illuminate/container Version ^13.0
ramsey/uuid Version ^4.7
Composer command for our command line client (download client) This client runs in each environment. You don't need a specific PHP version etc. The first 20 API calls are free. Standard composer command

The package waysnx/business-framework contains the following files

Loading the files please wait ...