Human direction, shared contribution, and copyright.

Aksbel Books are created through TheoryTrace, a system designed, developed, and managed by Mujirin. Its knowledge architecture, writing and citation standards, structure, tone, preparation stages, curation, verification, correction, and version history shape how each book is made. Language models assist the drafting process, while people initiate, review, improve, verify, and correct the evolving work through contributions that remain traceable.

This page explains how TheoryTrace recognizes those contributions and applies current copyright guidance. It is not legal advice; copyrightability and lawful use still depend on the contribution, material, jurisdiction, and circumstances involved.

Human creative direction TheoryTrace contributes a deliberately designed process. Protectable human expression, creative revisions, curation, selection, coordination, and arrangement are considered according to the applicable law and the facts of each contribution.
Language-model assistance Using a language model does not prevent protection for qualifying human contributions. The role of the model and the human contribution should remain transparent and traceable.
Generated-text overlap A generated passage can still reproduce protected expression. References improve traceability but do not grant permission to copy.
Digital replicas Current risk is low because Aksbel produces educational text and mathematical covers, not realistic cloned voices or likenesses.
Fractal covers TheoryTrace renders them from independently implemented mathematical rules without importing third-party artwork.

How Aksbel records contribution

TheoryTrace applies its human-designed knowledge architecture, editorial rules, reference standards, tone, and staged workflow to a learning objective proposed by a user.
A language model assists with drafts inside that workflow; its output is organized, reviewed, corrected, and developed through TheoryTrace rather than published as an untracked chat response.
Every substantive edit creates a new version. Earlier versions, editors, timestamps, corrections, and verification records remain traceable.
Initiators, verifiers, editors, and contributors whose corrections are applied receive role-based recognition in contribution history and citation metadata.
Copyright protection follows the protectable human creative contributions and applicable law, including qualifying expression, revisions, selection, coordination, or arrangement.

Aksbel is built as a shared effort to improve knowledge. TheoryTrace welcomes careful collaboration and is grateful to everyone who contributes ideas, review, correction, expertise, and time in good faith.

How to cite an Aksbel book and its documents

Cite the smallest unit that supports the statement you use. Use the document-level citation for a claim, definition, equation, example, or passage from one chapter or child document. Use the whole-book citation when referring to the book as a complete learning work, its overall structure, or its collective scope.

Document citation: `@inbook`

Records the exact document title inside its book, the current recorded authors and contributors for that document, publication year, publisher, URL, document and section identity when available, status, verifier and verification time, creation and update times, latest saved version, and the number of version snapshots.

Whole-book citation: `@book`

Records the book title, Mujirin, the recorded initiator and whole-book contributors, publication year, TheoryTrace Library as publisher, the live book URL, and a concise contribution note. Initiation is recorded once; document creation, verification, and recorded edits are counted as distinct contribution events.

TheoryTrace keeps the live document separate from its immutable version snapshots. Before a substantive change, the existing state is preserved; the edit, rename, status change, accepted correction, or other recorded change then creates a successor snapshot with its contributor, time, status, and verification record. An applied correction is attributed to its proposer and a previously verified document returns to review until the corrected version is verified. Earlier snapshots remain available in Versions and are not overwritten.

The copy-citation controls on each Aksbel document generate BibTeX from the current database record. For reproducible work, prefer @inbook, retain the URL and version details present in its note, and record your access date in your own reference manager when required by the publication style. Verification identifies who reviewed a specific version and when; it is attributable review evidence, not an automatic guarantee of truth.

Live example: Fadhilah Surat-Surat Al-Qur’an

These examples are generated from the book's current TheoryTrace records whenever this page is opened, so attribution, verification, dates, and version information follow later recorded changes.

Open book Open cited document View its versions

Whole book

@book{Mujirin2026FadhilahSuratSuratAlQurAn,
  title = {Fadhilah Surat-Surat Al-Qur’an},
  author = {Mujirin and Ade Dedi Pamungkas},
  year = {2026},
  publisher = {TheoryTrace Library},
  note = {Aksbel Book Series; created by the TheoryTrace system developed by Mujirin; whole-book recorded co-author/contributor shares: Ade Dedi Pamungkas (27%)},
  url = {https://theorytrace.com/projects/fadhilah-surat-surat-al-quran/}
}

Document: Pendahuluan

@inbook{Mujirin2026Pendahuluan,
  title = {Pendahuluan},
  author = {Mujirin and Ade Dedi Pamungkas},
  booktitle = {Fadhilah Surat-Surat Al-Qur’an},
  year = {2026},
  publisher = {TheoryTrace Library},
  note = {Aksbel Book Series; TheoryTrace document; section: Pendahuluan / Pendahuluan; status: Verified; verified by Ade Dedi Pamungkas at 2026-07-16 15:42 KST; created: 2026-07-16 12:28 KST; last updated: 2026-07-16 15:42 KST; document author: Mujirin; latest saved version by: Ade Dedi Pamungkas; latest version saved: 2026-07-16 15:42 KST; latest version verified by: Ade Dedi Pamungkas at 2026-07-16 15:42 KST; version snapshots: 3; created by the TheoryTrace system developed by Mujirin},
  url = {https://theorytrace.com/projects/fadhilah-surat-surat-al-quran/documents/pendahuluan/}
}

Review and reporting

Verification is a recorded judgement about an exact document version, not a guarantee of truth, originality, or legal clearance. Readers should consult original sources for important claims and quotations.

If you find an error, suspected plagiarism, an unacknowledged source, or an inaccurate quotation, select the relevant passage and use Correct or Report. Include the original work, author, URL, page, and supporting explanation when available. Reports request review; they do not themselves establish that a violation occurred.

Responsible publication

Generated passages still need source-overlap controls and human review before high-stakes or commercial publication.
Model training, output-use rights, retention, and contractual protections depend partly on the external model provider and its current terms.
Copyright, attribution, and publication requirements differ by jurisdiction. Indonesian law and any country of publication may require separate review.

Primary guidance

Back to About Explore Aksbel books