accounting-archetype-mapper

Transform domain requirements into accounting-style value flow models with traceability.

40|39|Updated Apr 1, 2026

Search Tags:#audit-trail #domain-modeling #resource-allocation #double-entry #accounting-archetype #value-tracking #ledger-design

Ready to run

npx skills add https://github.com/Architekt-Jutra/architekt-jutra-code --skill accounting-archetype-mapper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: accounting-archetype-mapper
Source: https://github.com/Architekt-Jutra/architekt-jutra-code/tree/main/week7/5-znanewzorce-demo/accounting-archetype-mapper
Command: npx skills add https://github.com/Architekt-Jutra/architekt-jutra-code --skill accounting-archetype-mapper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates the guesswork and inconsistency in modeling systems that track quantifiable value (such as loyalty points, data quota, inventory, or leave days) by providing a standardized, proven accounting archetype workflow that ensures traceability, reversibility, and full auditability for all value changes.

Core Features & Use Cases

Archetype Fit Testing: Automatically validates if a domain is suitable for the accounting archetype, avoiding misapplication to state machines or workflow systems.
End-to-End Domain Mapping: Transforms domain requirements into complete accounting models including account definitions, double-entry transaction mappings, validity rules, and allocation strategies.
Use Case: For a loyalty points program, this Skill models earn, spend, expiry, and refund flows, distinguishes between earned, purchased, and promotional points, and defines rules for which point source is consumed first.

Quick Start

Use the accounting-archetype-mapper skill to transform your loyalty points domain requirements into a complete, implementable accounting-style value flow model with full audit trail support.

Frequently Asked Questions about accounting-archetype-mapper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a double-entry ledger model for loyalty points and data quota tracking?▼

A double-entry ledger model for loyalty points tracks value flows by defining account definitions, transaction mappings, and validity rules for accumulation and consumption. This ensures full traceability and auditability for all value changes across the system.

What is the best way to model reversible transactions and refunds in a value-tracking system?▼

Modeling reversible transactions in a value-tracking system requires defining specific reversal mechanisms within an accounting-style value flow model. This approach supports refunds and multi-source allocation while maintaining a complete audit trail for every operation.

When should I use an accounting archetype for domain modeling instead of a state machine?▼

You should use an accounting archetype for domain modeling when your system involves accumulation, consumption, transfer, or expiry of quantifiable value like credits or leave days. State machines are better suited for workflow systems rather than auditable value-tracking domains.

How do I implement allocation strategies that define which value source is consumed first in a points system?▼

Implementing allocation strategies for value consumption involves defining rules within your accounting model that specify transaction mappings and validity constraints. This determines which point source, such as earned or promotional points, is depleted first during operations.

Does this accounting archetype approach work for tracking inventory units and leave days with expiry rules?▼

Yes, the accounting archetype approach works for tracking inventory units and leave days by applying double-entry transaction mappings and validity rules. It handles expiry, accumulation, and transfer of quantifiable value while ensuring full auditability across all domain resources.