For venture studio adjacency can we get the DEX recommendation

Recommendation

If the locking and audit trail are material to your LP or auditor commitments, I'd suggest raising this as a feature request with the Decile team directly, since audit trail functionality is something the community has been asking for. In the meantime, the data room + manual amendment log approach is the most defensible workaround available today.

Origin: 

We add to every portfolio company an assigned one of three deal source designations at the time of initial investment:
STUDIO_ORIGINATED, the company was built inside or directly by the Grow Cycle Solutions studio before the fund invested.
STUDIO_REFERRED, the company was introduced to the fund by the studio or a studio partner but was not built by the studio.
MARKET_SOURCED, the company was sourced through the fund's independent deal flow, with no studio involvement in the introduction.
This designation is set at closing, timestamped, and locked against editing. Any subsequent change requires a dated Amendment Log entry stating the prior value, the new value, the reason for the change, and the name of the person who made it. The Amendment Log is available to LPs and auditors on request.
in decilehub?

DEX RESPONSE - This is a great question about whether Decile Hub's data model can accommodate a custom deal-source designation field with the locking and audit-trail behavior you've described. Let me search the knowledge base for what's actually supported.
Here's an honest breakdown of what Decile Hub can and cannot do for your deal-source designation policy:

What Hub supports today

Hub does have custom fields on deal pipeline records (including a custom dropdown field with limited options, per community replies). You could create a dropdown called something like "Deal Source Designation" with the three values: STUDIOORIGINATED, STUDIOREFERRED, and MARKET_SOURCED. That covers the core tagging requirement.

What Hub does NOT natively support

The specific controls your policy requires go beyond what Hub currently offers out of the box:

  • Field locking at closing. Hub does not have a native "lock this field after a certain event" mechanism. Nothing prevents a team member from editing the designation after it is set.
  • Timestamped designation at closing. Hub tracks when records are created and modified generally, but there is no native "set this field at closing and timestamp it" workflow.
  • Amendment Log with prior value, new value, reason, and author. Hub does not have a structured amendment log for custom field changes. The community has explicitly requested audit trail functionality for field edits and commitment changes, and as of the knowledge base results, it is not yet available as a built-in feature.
  • LP/auditor-accessible Amendment Log. There is no native mechanism to expose a field-change history to LP data room viewers.
Practical workaround

You can approximate this policy inside Hub using a combination of:

  1. A custom dropdown field on the deal/organization record for the designation itself.
  2. A notes or text field (or a pinned note on the deal) where you manually log any amendment: prior value, new value, reason, date, and name of the person who made the change.
  3. A document in the LP data room (a simple Amendment Log file) that you update and version whenever a change is made, giving LPs and auditors access to it there.
The enforcement and locking, though, would be procedural (team discipline and process) rather than technical. Hub cannot currently prevent an edit or auto-enforce the amendment requirement.