FOUNDRY
CONFIGURATION

Reference data · 14 entities, 18 territories, 13 certificate types

The lists every other screen reads from. Changes here are drafted, approved by a second owner, then applied on the next sync.

Sites & entitiesTerritoriesCertificate typesERP connections & field mappingGrouping rules

How each family is grouped

FamilyLevel 1Level 2Level 3Level 4Level 5Level 6Built in the treeName parserOwnerState
LoksetResin speedDiameter (mm)Length (mm)Temperature gradePackCertification build6 of 6 on HS 23×900 · 3 of 6 elsewhere9 name patterns · regex + AURAP. LanganLive
Capsule resinResin speedDiameter (mm)Length (mm)Temperature gradePack—0 of 5 — SKUs still ungrouped2 patterns · draftP. LanganDraft
Tekpak——————No scheme definedNo rule configuredUnassignedNot configured
Polyurethane & silicateChemistryComponent ratioViscosity gradeTemperature gradePack sizeCertification build2 of 6 built4 patterns · regexH. VogelLive
Cementitious groutsStrength classSet profileBag size—Pallet configurationCertification build0 of 5 built3 patterns · regexH. VogelLive
Bolts & anchorsThreadLength (mm)CoatingHead typePackCertification build0 of 6 built6 patterns · regex + AURAS. WhelanLive
Ventilation & sealingTypeSizeMaterial grade—Pack—0 of 4 built2 patterns · draftUnassignedDraft
Grouping rules decide what counts as the same product. Changing one re-groups every entity on the next run, so a change is drafted, simulated against the live catalogue, then approved.

Canonical attribute schema

AttributeTypeUnitSource precedenceMay confirm
DiameterNumbermmParsed name → ERP attribute → manualProduct data owner
LengthNumbermmParsed name → ERP attribute → manualProduct data owner
Cartridge weightNumberkgERP net weight → AURA reconciledTechnical
Set timeRangesSpec sheet → ERPTechnical
Ex-works costMoneyReporting currencyERP standard cost → production orders → fileFinance · read-only in Foundry
Shelf lifeNumbermonthsERP → spec sheetTechnical
CertificatesList—Foundry only — never read from ERPCompliance
Sellable territoriesDerived—Certificate rules, recomputed nightlyCompliance · rule change only

What AURA is allowed to do

AURA groups on its own above 80% confidence and applies matches at 95% and above after four hours. It may never create a hierarchy level, change a certificate, or grant a selling right — those three stay with a person, and every decision is recorded against a name.
Confidence floor
80%
Below this, a human decides
Automatic application
On · ≥95%
4-hour objection window
Never automated
3 actions
create a hierarchy level, change a certificate, grant a selling right
Audit retention
7 years
Every field change, with its source
Changing the floor changes what the AURA inbox holds back for a person. It does not re-open anything already decided.