Reproducibility Guide Plain HTML/CSS/JS GitHub Pages ready

Implementation notes grounded in what the paper actually provides

This page explains what is directly reproducible from the repository, what has been reconstructed for presentation only, and how the paper's cloud ERP integration ideas should be interpreted without overstating them as completed deployment code.

Artifact Map

Repository components and their purpose

Curated paper structure

  • docs/assets/papers/AI-Cloud-ERP-Accepted-Manuscript-Encrypted.zip is the protected PDF download.
  • docs/assets/papers/AI-Cloud-ERP-Accepted-Manuscript-LaTeX-Source-Encrypted.zip is the protected LaTeX-source download.
  • paper/ remains the repository working directory used to curate and refresh source assets.

Web and presentation layer

  • docs/index.html is the main research portal.
  • docs/report.html, docs/poster.html, and docs/implementation.html provide alternate views.
  • docs/assets/ contains published site images, charts, data, and the encrypted manuscript archives.

Data layer

  • data/baseline_metrics.csv and data/attention_scores.csv are exact table exports.
  • data/reconstructed_training_curves.csv is presentation support data only.
  • data/research_data.json feeds the docs site and keeps provenance in one place.

Automation

  • scripts/generate_visualizations.py copies assets, writes data exports, and builds the SVG gallery.
  • scripts/refresh_assets.sh reruns the generator.
  • scripts/check-js.sh checks the website JavaScript syntax with Node.
Experiment

Reported experimental setup from the paper

Environment

  • Google Colaboratory
  • NVIDIA Tesla T4 GPU with 12 GB VRAM
  • Python 3.10
  • TensorFlow 2.13
  • Pandas and Scikit-learn
  • Matplotlib for training-curve visualization

Important repository boundary

The environment above is reported in the manuscript, but the repository does not contain runnable notebooks, package lockfiles, or the ERP dataset needed to replay training end-to-end.

The repo therefore focuses on faithful publication packaging rather than claiming full training reproducibility that the source bundle does not support.

Cloud Path

How to read the cloud integration claims correctly

Dynamic resource allocation

R_i = alpha_i * C_i

Interpreted as attention-informed scaling of module compute demand.

Fault-prone dependency centrality

D_k = sum I(M_k in T_i) * alpha_ik

Used to reason about modules that may require stronger failover strategies.

Microservice inference

f_theta: T -> c -> y_hat

Represents the prediction engine as a stateless AI service within cloud-native ERP architecture.

Scope statement

The paper describes a formal integration pathway for cloud ERP use, but it also states that a full physical deployment was not performed in the current study. The website preserves that distinction everywhere.

Workflow

How to refresh and maintain the public artifact

Refresh generated assets

bash scripts/refresh_assets.sh

This updates the CSV exports, combined JSON, copied paper assets, and SVG visualizations.

Check site JavaScript

bash scripts/check-js.sh

If Node is installed, the script validates docs/script.js with node --check.

Metadata normalization

The repository aligns the public citation and site metadata to the official IEEE indexing record because the local LaTeX bundle still shows a stale conference header from an older template.

Why the training curves are labeled

The interactive line charts are useful for the portal, but they are explicitly marked as reconstructions because the repo includes only the rendered figures, not raw epoch logs.

Deploy

GitHub Pages publication path

Pages configuration

  1. Push the repository to GitHub.
  2. Open Settings -> Pages.
  3. Select Deploy from a branch.
  4. Choose the default branch and the /docs folder.

Expected site URL

https://anis151993.github.io/AI-and-Cloud-Computing-in-Business-Systems-A-Hybrid-Model-for-Enhancing-Enterprise-Resource-Planning/

The root repository also includes a markdown deployment guide in the GitHub repo for contributors who want the non-site version of the same workflow.