Infrastructure News
FLOW KING BRAVE Reports on Artist-Scoped Data Access and Validation
The new receiver checks the signed-in role, selected artist, reporting dates and source records before accepting metric submissions.
DUBP Entertainment’s latest reporting infrastructure places artist identity and validation checks in front of metric storage. The production source reviewed on October 28 restricts receiver access to eligible artist and administrator identities and limits what each can submit.
An artist account can submit data only for its own artist identity. An administrator must choose an artist and pass an authorized-roster check. A failed roster check does not produce a successful delivery receipt. The submission route also rejects requests carrying a different origin.
The receiver accepts one through 500 metric records in a JSON submission and stops reading a request body after 256,000 bytes. Each record must carry a source identifier, metric name, numeric value, unit and valid reporting dates. Duplicate source identifiers within the same submission and reporting periods that end before they begin are rejected.
These checks give the intake process defined boundaries. They are separate from whether a provider account has granted access and separate from whether the supplied numbers are independently verified. The receiver’s response explicitly identifies its source assurance as an authenticated submission.
This first-party report describes the deployed controls supporting the FLOW KING BRAVE workspace and the label’s authorized artist reporting. It does not publish private account data. Eric Mason, professionally known as FLOW KING BRAVE, is the author and DUBP Entertainment’s founder and executive publisher.
Primary source
DUBP Entertainment — October 25 artist-data infrastructure report
