Skip to content
TheChatArchiveThe Chat Archive
gpt-4.1-mini-2025-04-14· OpenAIAi2 WildChat-4.8M (AI2)

Like you know, we supposed to, you know, prepare this high level design and then we…

  1. User

    Like you know, we supposed to, you know, prepare this high level design and then we should discuss with beam and prepare some data contract, right.

    Because in a strategic feed how we will send a stock data to them, right? So because right now, whatever is sending that is not enough, right? So there are some additional field also need to. Into them and then. Apart from this, like a structure and everything need to be discussed with them as well, right?

    But here what we are talking about, I think we should get a discuss with beam as well. Right? And then? Data mapping and data contract also see we have to discuss with beam, right and then maybe at the same time then we have to analyze and understand if something we need from partner then we will start discussing with partner as well. I think there was a discussion as well. OK, so maybe I think that.

    so design and then discussion with beam and prepare a data contract.

    And then from partner perspective for stock? I mean, we need to have some clarity around that. I think whatever we are asking partner should be able to provide, but they are also taking at their end how they can bring the intransit information as they was updating earlier. So that alone might be like, I mean we. Need to discuss with partners, but other than that the other fields they are OK to share it across. But we need to discuss it beam as well and confirm if I mean from the data contract SLS from the design perspective.

    Yeah, sure. Lalitha OK. So let's see. Let's first try to get it closed with beam that is internal one, because then only we do understand, right? So what exactly expectation of beam, right? What kind of what? What is the data they require? OK. And then based on that, you know we can prepare and then discuss with partner.

    In documentation, strategic stock finance schema with validation rules. KA

    ....explain in brief

  2. Assistant

    Certainly! Here's a brief explanation of your points:

    1. High-Level Design Preparation: First, create a high-level design for how stock data will be sent in a strategic feed.

    2. Discussion with Beam: It's essential to discuss this design with Beam (an internal team or system) to understand their exact requirements. This includes:

      • The data structure
      • Additional fields needed (beyond the current data)
      • Data contract and data mapping specifics
    3. Data Contract: After understanding Beam’s expectations, formalize a data contract that defines what data will be exchanged, in what format, and any validation rules.

    4. Partner Coordination: Once the internal agreement with Beam is settled, evaluate what data or information is required from partners. Have discussions with partners about:

      • Their capability to provide the requested fields
      • How they handle specific data like in-transit stock information
    5. Validation and Documentation: Document the final strategic stock finance schema with clear validation rules to ensure data quality and consistency.

    Summary: Prepare a design → Discuss with Beam to finalize data contract and structure → Then engage partners for data provision → Document everything with validation rules.

    Let me know if you want me to expand on any part!